toolintegrator SOAP UI TEST Usersguide

toolintegrator SOAP_UI_TEST Usersguide October 24, 2013

UsersguideMOBILE_CLOUD_TEST

typetoolintegrator.com

(c) jesper mortensen 2013-2014

[email protected] Page 1/17

mailto:[email protected]


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

Creating a MOBILE_CLOUD_TEST............................................................................3Device selection and testconfigurations..................................................................5Covering requirements with test-configurations.......................................................9

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

Appendix A: Configuration Settings................................................................................16

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-2014




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

➔ Create a MOBILE_CLOUD_TEST

◦ Linking it to a Script the Perfecto Mobile Cloud

◦ Select a mode for device selection during execution

➔ Edit Settings

➔ Create and edit Test Configurations (controlling testdata)

Creating a MOBILE_CLOUD_TEST

To create a MOBILE_CLOUD_TEST you press “New Test” as you would normally do, but on the drop-down in the right corner (that is set to MANUAL as default) you select the MOBILE_CLOUD_TEST.




If you switch to the Script View of the newly created test you will see this:

If this is the first test you create after a client installation you need to configure the access to the Perfecto Mobile Cloud. Press the button to access the configuration and set the relevant paths, urls and credentials.

See appendix A for details about the different settings.

For client installation please see toolintegrator_ MOBILE_CLOUD_TEST_Installation.pdf

To link the test to a script in the cloud press the button at the “scriptname” line of the top pane.

This opens a dialog you can use for seleting a script in the Perfecto Mobile Cloud Script Repository:




After selecting a script, the plugin populates with different script information:

The “Script display” and “Parameter display” areas are only informational. I order to change the script flow or the parameters you will need to change them on the script in the Perfecto Mobile Cloud.

The “Device selection method” is integrated with testconfigurations in order to make it easier to get a script running on multiple devices.

Device selection and testconfigurations

The drill-down button right of the device selection dropdown will give you a list of available devices in you cloud. By selecting a number of devices you automatically creates a test-configuration for each selected device. When you later on drag the test into a TestSet in TestLab, each selected device will become seperate “Test in TestSet” (aTest Instance).




If you switch to the Test Configurations tab after changing the device selection you cansee that the testconfigurations are created based on your selection:

The test-configurations will automatically keep both the deviceid and the model of the selected devices. But later on when running the test in testlab the “device selection




method” will decide which one to use when looking for a device to execute on.

By changing the device selection method the testconfigurations are reset:

On the Test Configurations tab you can see the changed configurations:

If the test in the Perfecto Mobile Cloud has runtime parameters (besides the default dut




parameter) they will be picked up by test MOBILE_CLOUD_TEST, and you can give them a value on the Test Configurations tab.

This enables you to control testdata from inside HP Quality Center/ALM eg. running the same script on the same device with many diffent values, you would have to edit add thencessary testconfugrations manually in order to do this. (There is only support for the “static data” setting in the Test Configurations tab).

Covering requirements with test-configurations

When testing on multiple platforms/devices the build-in traceability in HP Quality Center/ALM it a perfect tool for tracing status and progress.

By keeping “functional requirements” and “platform requirements” seperate the status of a given feature can be tracked. Here is the requirements in the requirements module:

By covering the requirements with testconfigurations you can now track the progress and status.

When covering functional requirements they are linked to all testconfigurations on the test:




When covering platform requirements, only the test-configurations relevant for the specific requirement are selected:

Each MOBILE_CLOUD_TEST will be covered by a mix of functional and platform requirements, based on the testconfigurations:

This only has to be done once for each test. Later on when adding the test to the TestSetthe testconfigurations will follow the test and the requirements coverage will be in place.




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:

As all tests are executed in the cloud, the “Run host” setup that enables HP Quality Center/ALM to distribute the execution to multiple execution hosts, is really not relevant.

Just enable Run All Tests Locally.

Then press Run All.

Because HP Quality Center/ALM would normally execute the tests sequentially, the MOBILE_CLOUD_TEST uses its own scheduler. This means that the execution as seen by the Automatic Runner is over as soon as the test is handed over to this scheduler:




The MOBILE_CLOUD_TEST Scheduler then picks up the testinstances and executes them in parallel on the devices in the Perfecto Mobile Cloud:

If a testinstance for some reason cannot be executed rightaway the Waiting fo” column will display the reason. There might not be a device free that fullfils the required specifications (devicid or model) or you might because of the business logic have specified an execution order in the TestLab/Execution Flow tab.




When the execution is over you can close both the MOBILE_CLOUD_TEST run status view, and the Automatic Runner.

I the automatic runner was closed before all tests finished you might need to update the TestSet in order for the execution status to show correctly:

The Last Run Report is available at the bottom of the view, but you can also drill down on each testinstance to see older runs.

At the end of a Run the Run-report is copied from the Perfecto Mobile Cloud, and uploaded to HP Quality Center/ALM as an attachment to the run.

You can use the open report button to open the report in a browser.




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 and all available deviceinfo 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 notavailable for the MOBILE_CLOUD_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:

The defect is created with the same attachments as the run.

The defect is linked to the run and to the testinstance, for traceability:




Appendix A: Configuration SettingsBy pressing the button on the Test Script view of the TestCase or on the Report View of the run, you can edit the different settings:

The settings are stored in a file in the QC Client folder. This means that the settings mustbe updated on all clients that uses the plug'in.

Setting Use

Temp folder The MOBILE_CLOUD_TEST uses this for all sorts of temporary stuff. The default value is taken from the users profile. Normally there is no reason to change this

Log The folder where the log is located. As default this is the same as the temp folder.The log is named: MOBILE_CLOUD_TEST_LOG.txt

Log details This is the level of detail in the log with:

1 DEBUG2 WARNING3 INFO




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 [email protected]

QC Client 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.

Cloud URL The base URL of your Perfecto Mobile Cloud. You need to set is as http or https whatever fits your cloud

Cloud User The extension works through the Perfecto Mobile Cloud Rest API. This users need the permissions to use this API.

Cloud Pass The password is stored encrypted. Use the Set Cloud Password button to change this value.







Documents

toolintegrator SOAP UI TEST Usersguide