Usersguide SELENIUM_TEST type

Size: px

Start display at page:

Download "Usersguide SELENIUM_TEST type"

Nora Booth
6 years ago
Views:

1 Usersguide SELENIUM_TEST type toolintegrator.com (c) jesper mortensen Page 1/23

2 Table of Contents Copyright...2 Testplan Creating and editing Testcases...3 Creating a SELENIUM_TEST...3 Understanding the CurrentSelenium JAVA project...7 Finish editing and upload files...9 Editing Settings...10 Create and Edit Test Configurations...10 Test Configurations...11 Link to requierements for traceability...12 TestLab Executing tests...13 Creating a defect from the Run Results...16 Appendix A: Configuration Settings...18 Appendix B Importing the CurrentSelenium workspace...21 Initialization...21 Eclipse...21 NetBeans...23 Copyright All trademarks mentioned belong to their owners, third party brands, product names, trade names, corporate names and company names mentioned may be trademarks of their respective owners or registered trademarks of other companies and are used for purposes of explanation and to the owner's benefit, without implying a violation of copyright law. (c) Jesper Mortensen sales@toolintegrator.com Page 2/23

Testplan Creating and editing Testcases On testplan you can administer the SELENIUM_TEST type: Create a SELENIUM_TEST Upload a JAVA TestSuite and TestCases Edit the project Edit Settings Create and

3 Testplan Creating and editing Testcases On testplan you can administer the SELENIUM_TEST type: Create a SELENIUM_TEST Upload a JAVA TestSuite and TestCases Edit the project Edit Settings Create and edit Test Configurations (controlling testdata) Creating a SELENIUM_TEST To create a SELENIUM_TEST you press New Test as you would normally do, but on the dropdown in the right corner (that is set to MANUAL as default) you select the SELENIUM_TEST. sales@toolintegrator.com Page 3/23

If you switch to the Script View of the newly created test you will see this: By pressing the upload button you can select a Selenium TestSuite project and upload it

4 If you switch to the Script View of the newly created test you will see this: By pressing the upload button you can select a Selenium TestSuite project and upload it to the testcase. If you have just installed the extension you might get a warning about the parts of the configuration that is missing: sales@toolintegrator.com Page 4/23

5 Press the button to access the configuration and set the relevant paths. (See appendix A for details about the different paths you need to set.) If the paths are all set, you should see this view on the Test Script tab: Press the upload button and select the JUnit TestSuite that you want the test to keep. The upload functionality will parse the TestSuite and try to find all the referenced testcases (It expects the testcases to be located in the same folder as the TestSuite). sales@toolintegrator.com Page 5/23

6 You can now select an editor and start editing. To edit the test you press the Tests button. The view now changes to this and the editor launches: Edit Page 6/23

If this pop-up appears: The editor is not properly initialized. See in appendix B how to intialize eclipse and NetBeans in order for editing to work.

7 If this pop-up appears: The editor is not properly initialized. See in appendix B how to intialize eclipse and NetBeans in order for editing to work. Understanding the CurrentSelenium JAVA project The following will use eclipse as example, but basically the same things can be done in NetBeans. All tests will use the same temporary JAVA project called CurrentSelenium. This means when you start editing by pressing the Edit Tests button all JAVA source files and the project file is deleted the JAVA source files from the current test is downloaded to the project a new project file is created with the relevant classpaths etc. the editor launches. If the editor is already open it gets the focus As the editor might be in a state with files open from the last test you edited and references in the Package Explorer from the last test hat you have to do is: Close all open files in the edit view Refresh the package explorer And you can now start editing. The indidual TestSuites and TestCases are expected to be quite simple, all TestSuite and TestCase code is expected to be in default package. The upload-download functionality do not support code in subfolders. Besides the TestSuite and TestCases you uploaded originally an additional.java file is found in the project: TestParameters.java. This file is used for transferring testdata from HP QC/ALM to the test at runtime. sales@toolintegrator.com Page 7/23

8 As a commentary in TestParameters.java you can find the code you need to control the browser choice from HP QC/ALM. You declare the parameters you need to access from HP QC/ALM as static strings which gives you a content that might look like this: sales@toolintegrator.com Page 8/23

9 And you move the rest of the code to the SetUp of each TestCase: (Any other parameter you might need to give a value at runtime can be declared in TestParameters.java and used in the TestCases) From here on its standard java-editing. Just remember: Keep all code in the default package TestParameters.java will only support static String types Finish editing and upload files When you are satisfied with the TestSuite and TestCases you can close the editor (which will automatically upload the files) or you can press the End editing and upload files button in the Script View. This will upload the files, but the editor stays open and can now receive the files for the next test you want to edit. When uploading the SELENIUM_TEST parses the TestParameters.java file and synchonizes the test parameters in HP QC/ALM with the content of the file. sales@toolintegrator.com Page 9/23

10 Editing Settings By pressing the settings: Info and Settings button you get a dialog that allow you to edit different See appendix A for documentation of the different settings. Create and Edit Test Configurations With Test Configurations you can do many different things: Running the same test with different input data and validations Link to requirements for traceability sales@toolintegrator.com Page 10/23

11 Test Configurations The testconfigurations can be used to keep different testdata for the same test. This can be used for all sorts of testdata, but a special case is the browser choice, which is supported by some added functionality in the SELENIUM_TEST. If you press the Create TestConfigurations for different browsers button SELENIUM_test will create a TestConfiguration for each browser derfined in variable under Info and Settings and then dislay a confirmation like: the the browsers If you switch to the TestConfigurations view of the test you can see the three configurations that were added: sales@toolintegrator.com Page 11/23

12 Link to requierements for traceability When linking to requirements the the same functionality that you are used to from any other HP Quality Center/ALM test are used: Page 12/23

Tests Locally. (In the HP Quality Center/ALM documentation you can find a description on how to define and assign multiple hosts.

13 TestLab Executing tests In TestLab you can add your tests to a TestSet like any other test. Each TestConfiguration will create a testinstance: When you press Run Test Set you get the Automatic Runner where you can keep track of the execution: When trying this out just enable Run All Tests Locally. (In the HP Quality Center/ALM documentation you can find a description on how to define and assign multiple hosts. You just have to make sure that the run-hosts is configured correctly with all settings and paths etc.) Press Run All and the tests starts executing. The testrunner is launched in the background. After the tests has run the status can be seen in the Automatic Runner and the status field in TestLab is updated when you close the runner. sales@toolintegrator.com Page 13/23

As the tests execute you can follow their

14 As the tests execute you can follow their status in the testrunner. At the end all tests have been run and you can close the testrunner: When closing the runner the TestSet in TestLab is automatically updated with the status: Page 14/23

On each run all files necessary to recreate the run is attached (given that they are

15 In the Last Run Results view at the buttom of the TestSet view you can see the report from the execution. For older exectutions you have to open the run history. On each run all files necessary to recreate the run is attached (given that they are downloaded to a folder and executed on a host with the same paths as the run-host): sales@toolintegrator.com Page 15/23

Creating a defect from the Run Results If you press the create defect button you will get a dialog: -With the text from the error log inserted into the description field, you can just edit it if

On the Required fields tab all fields that are defined as required in the HP Quality Center/ALM project are shown: The reason that only the required fields are shown is that all sorts of

16 Creating a defect from the Run Results If you press the create defect button you will get a dialog: -With the text from the error log inserted into the description field, you can just edit it if appropriate. On the Required fields tab all fields that are defined as required in the HP Quality Center/ALM project are shown: The reason that only the required fields are shown is that all sorts of field-customization might be in place in a given HP Quality Center/ALM project, and this customization is not available for the SELENIUM_TEST extension. These fields should get you started on the defect. Press Create and you can find the defect in the defects view and fill out additional fields. The defect has all the logfiles from the Run attached and are linked to the Run and to the testinstance: sales@toolintegrator.com Page 16/23

(given that they are downloaded to a folder and executed on a host

17 The defect is created with the same attachments as the fun, which means that the defect can be reproduced using only the attachents (given that they are downloaded to a folder and executed on a host with the same paths as the run-host): sales@toolintegrator.com Page 17/23

Appendix A: Configuration Settings As any java related technology you need to set som paths both to the executable parts and to the different libarary jars.

18 Appendix A: Configuration Settings As any java related technology you need to set som paths both to the executable parts and to the different libarary jars. You can set the paths as you see them in the explorer but the settings view will turn them into old style DOS paths removing spaces. Setting Temp folder Use The SELENIUM_TEST uses this for all sorts of temporary stuff. The default value is taken from the users profile. Page 18/23

19 Log Log details Normally there is no reason to change this The folder where the log is located. As default this is the same as the temp folder. The log is named: SELENIUM_TEST_LOG.txt This is the level of detail in the log with: 1 DEBUG 2 WARNING 3 INFO QC Client JAVA_HOME ANT_HOME SELENIUM_JAVA_LIBS _HOME netbeans_exe eclipse_exe java_editor java_workspace Default is 3. If for some reason the extension gives you trouble set it to 1 and repoduce the problem. And send the log to support@toolintegrator.com Is the folder where the QC Client is located. The extension tries to find this information in the registry, but if for some reason you have multiple QC Client installations in different places you might want to point this to the one that is used. This is where the JDK you want to use is installed. No default value. This is the main folder for the ANT toolkit. The SELENIUM_TEST expects to find ant.bat in the %ANT_HOME%\bin folder and the libraries in the %ANT_HOME%\lib folder. The extension is tested using ANT version 1.9.2, but most recent versions should be ok. No default value. These libraries you get as a.zip from here: The extension is tested with but most recenct versions should work. No default value. This is the path to the netbeans executable. If you want to be able to use NetBeans for script development you shoud set this. No default value. This is the path to the eclipse executable. If you want to be able to use Eclipse for script development you shoud set this. No default value. This is set by the extension, just leave it alone. This is the path to the (NetBeans and/or Eclipse) workspace. In this workspace the CurrentSelenium (NetBeans and/or sales@toolintegrator.com Page 19/23

20 driver_server_path Eclipse) project is created, which is used for editing the current test. All.java files will be deleted in the CurrentSelenium folder before you download a TestSuite from HP QC/ALM so dont use this project for other things. For more details see Appendix B Importing the CurrentSelenium workspace This is the path to the folders for the different.exe files that are used for driving browsers. Each path is seperated by a semicolon ;. A path might look like this: C:\ProgramData\selenium-java \IEDriverServer_Win32_2.37.0;C:\ProgramData\seleni um-java \chromedriver_win32 browsers These paths are added to the system_path JAVA option when executing the tests, which means that you do not need to do this in your code. This is a comma-seperated list of browsers. This list is used for creating testconfigurations when pressing the button. The values will be used as the value for the BROWSER variable in the TestParameters.java. The list might look like this: IE,Firefox,Chrome sales@toolintegrator.com Page 20/23

Appendix B Importing the CurrentSelenium workspace The SELENIUM_TEST uses a temporary project called CurrentSelenium when editing TestSuites.

21 Appendix B Importing the CurrentSelenium workspace The SELENIUM_TEST uses a temporary project called CurrentSelenium when editing TestSuites. When you press the edit TestSuite button on a test, the workspace is cleared and the current test is downloaded to the workspace. When the editing is over you close the editor, or press the upload button and the.java files are uploaded back into HP QC/ALM. Your editor (Eclipse or Netbeans) must be made aware of this project in order for the editing to work. Initialization Set the java_workspace path in settings to the location where you have your java projects. Eclipse Press File/Import Press the edit TestSuite button and the CurrentSelenium project is created. This dialog tells you that the project was created: You now need to import the project into your editor for the first (and only) time. sales@toolintegrator.com Page 21/23

22 And thats it: Page 22/23

23 NetBeans Press File/Open Project And thats it. Page 23/23

Usersguide SOAP_UI_TEST type

Usersguide SOAP_UI_TEST type toolintegrator.com (c) jesper mortensen 2013 sales@toolintegrator.com Page 1/14 Table of Contents Copyright...2 Testplan Creating and editing Testcases...3 Creating a SOAP_UI_TEST...3