toolintegrator SOAP UI TEST Usersguidetoolintegrator.com/download/toolintegrator_SOAP_UI_TEST_Usersguide.pdf · toolintegrator SOAP_UI_TEST Usersguide October 24, 2013 the SOAP_UI_TEST

toolintegrator SOAP_UI_TEST Usersguide October 24, 2013

UsersguideSOAP_UI_TEST type

toolintegrator.com

(c) jesper mortensen 2013

[email protected] Page 1/14

mailto:[email protected]


Table of ContentsCopyright..........................................................................................................................2Testplan – Creating and editing Testcases.......................................................................3

Creating a SOAP_UI_TEST.........................................................................................3Editing Settings............................................................................................................6Create and Edit Test Configurations............................................................................6

Test Configurations.................................................................................................6Example – Testing with multiple endpoints..............................................................8Link to requierements for traceability.......................................................................9Enabling the All Tests option on the SOAP_UI_TEST.............................................9

TestLab – Executing tests...............................................................................................11Creating a defect from the Run Results................................................................13

CopyrightAll 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 2013




Testplan – Creating and editing TestcasesOn testplan you can administer the SOAP_UI_TEST type:

➔ Create a SOAP_UI_TEST

◦ Upload a project to the Test

◦ Edit the project

➔ Edit Settings

➔ Create and edit Test Configurations (controlling testdata)

Creating a SOAP_UI_TEST




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 SoapUI project and upload it to the testcase.




In the SoapUI Test dropdown you can select which TestSuite or TestCase in the SoapUI project the SOAP_UI_TEST in HP Quality Center/ALM represents.

When selecting a specific TestSuite or TestCase the Steps preview populates to help you remember the content of the Test Steps in the SoapUI project:

In the Project Properties area the properties defined at the project level of the SoapUI project displays. These properties are used to get testdata into the SoapUI project duringexecution (more about this in the “Create and edit Test Configurations” paragraph).

If you press the edit project button the project opens in SoapUI. And you can edit the requests and everything else as you are usedto.

When you are satisfied with your updates you have to close SoapUI in order for the SOAP_UI_TEST in HP Quality Center/ALM to pick up the changes.




Editing Settings

By pressing the Info and Settings button you get a dialog that allow you to edit different settings:

When displaying for the first time the SOAP_UI_TEST type will try to find the location of your SoapUI installation. If for some reason this fails, you need to set the path to the SoapUI.exe here,else you will not be able to edit or execute SoapUI tests.

You can change the other settings if you want to, the defaults should be OK for most installations

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

➔ By enabling the All Tests checkbox on the testcase you cna

◦ Use a TestConfiguration for each TestCase in the SoapUI test

Test Configurations

When you switch to the Test Configurations tab on the SOAP_UI_TEST in HP Quality Center/ALM you can see that the Project Properties in the SoapUI Project have been added to




the SOAP_UI_TEST and that a default Test Configuration with the values from the SoapUI properties has been set. If you delete the Actual Value the value from the SoapUI project will be used.

By adding more TestConfigurations you can execute the TestCase with different values.

The Override endpoint parameter can be used if you want to use a different endpoint than specified in the SoapUI project. If you leave it empty the default endpoint from the SoapUI project will be used.

When execution a SOAP_UI_TEST in TestLab the Actual Value is given to the testrunner.bat script that is part of SoapUI. Because the values are transferred as commandline parameters there are some limitations on what can be used. “Linefeeds” cannot be transferred, and complex values with xml markup might be a problem. If you for some other reason need project properties in the SoapUI project that cannot be transferred, just delete the Actual Value and the value insidethe SoapUI project will not be altered when executing the test.




Example – Testing with multiple endpoints

Default endpoint is used in the first testconfiguration:

Here the same values are tested on an alternative endpoint in the second testconfiguration:




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:

Enabling the All Tests option on the SOAP_UI_TEST

If you enable the All Tests option on the SOAP_UI_TEST a number of things change

➔ A testconfiguration is created for each TestCase in the SoapUI project

➔ A parameter TestCase is added to the SOAP_UI_TEST

This means that which testcase is executed in TestLab is now controlled by the TestCase parameter.




This way a larger SoapUI project can be traced. By covering different testconfigurations/TestCases with different requirements, you still know what requirements pass and fail.

You can still add and remove testconfigurations as long as you make sure that the Actual Value of the TestCase parameter points to a TestCase in the SoapUI project.

If you add or remove testcases in the project the testconfigurations will not be updated automatically. The reason for this is that deleting a testconfiguration in HP Quality Center/ALM automatically delete all testinstances with this testconfiguration, and this mightdestroy your test history.

To synchronize the TestCases in the SoapUI project use the synchronize button. This will remove add missing testconfigurations and remove testconfigurations where the TestCase is no longer present in the SoapUI project (see warning above).

After the synchronization is done you can see if anything was changed:




TestLab – Executing testsIn 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. As long as SoapUI is installed in the same path on all run hosts you should be OK. See below for limitations related to the All Tests setting)

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.




In the Last Run Result view you can see a summation and the different logfiles created:

If you click one of the logfiles in the bottom view a logviewer opens and you can see the logtext:




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 fildlcustomization might be in place in a given HP Quality Center/ALM project, and this customization is notavailable for the SOAP_UI_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 fromthe Run attached and are linked to the Run and to the testinstance:

Executing a SOAP_UI_TEST whit All Tests enabled

When you enable All Tests on the SOAP_UI_TEST (in TestPlan) a testconfiguration for each TestCase in the SoapUI project is added.

When adding a test with many testconfigurations to a TestSet you get a testinstance for each testonfiguration.

If some of your TestCases in the SoapUI project are dependent on data generated from other TestCases in the same project (that are run earlier), you need to transfer these data using Project Properties.

When a SOAP_UI_TEST with “All Tests” enabled executes in TestLab, the project is updated by the testrunner, and therefore the Project Properties of the SoapUI project have the correct values when the dependant testcase runs.

This means that you have to control the order in which the testcases are run, and also that you cannot run testinstances of the same testcase in parallel.



Documents

toolintegrator SOAP UI TEST Usersguidetoolintegrator.com/download/toolintegrator_SOAP_UI_TEST_Usersguide.pdf · toolintegrator SOAP_UI_TEST Usersguide October 24, 2013 the SOAP_UI_TEST