Integrating Selenium Tests into HP Quality Center/ALM as TestCases

Posted by Mufi on 9:37 PM with 1 comment

Integrating Selenium Tests into HP Quality Center/ALM as TestCases

By embedding the Selenium Test Suite directly in HP Quality Center as a TestCase you get:
  • A repository for your testing asset
  • Traceability from TestCases 
  • Full control of testdata
  • Execution history
  • Version control for your Selenium TestSuites and TestCases
  • Accellerated defect creation
  • Full use of the Selenium featureset
This release of the SELENIUM_TEST only supports JAVA based TestSuites and TestCases.

HP Quality Center/ALM as Repository for Selenium TestSuites

 

The test is created as any other test in TestPlan. The test type is SELENIUM_TEST and the test has fields and links just like any other test.
After creating the testcase the Selenium TestSuite is uploaded and it displays in the Test Script tab:


The different browsers for the test is defined on the Test Configurations tab. Other data for a datadriven test can also be defined here-


Keeping track of Executions with TestLab

In Test Lab the SELENIUM_TEST is added to a Test Set. When executing the test it launches with ANT and the results are saved back into Quality Center. In this way each Test in TestSet has a run history that contains repoports from both passed and failed runs:



Traceability

With HP Quality Centers build-in traceability:
  • Selenium TestCases can be linked to Requirements
  • Using testconfigurations different browsers can be tested using the same test, and tracking the results for each browser
  • Defects can be created with autogenereated run results, and linked to the test run

Version control

With HP Quality Centers build-in version control:
  • The Selenium TestSuite and TestCases can be versioncontrolled
  • The parametervalues entered in the testconfigurations can be versioncontrolled

Accellerated defect creation

 When creating a defect directly from the Run report, the defect gets:
  • The errorlog as Description
  • All log files as attachments
  • The JAVA source files and an ANT buildscript as attachments
It is automatically linked to the testinstance in the testset and to the run. All required fields are displayd in order to make sure a valid defect is created.




Source : http://toolintegrator.com/index.php/selenium-integration