Since I’ve had so many requests (the latest being today), and since I’m working on something very similar for a current client, I decided to take some time today to respond in detail about integrating QC with JUnit & Selenium.
The steps I’ve used for Selenium / QC integration are:
1. Write tests with Selenium using an open source test framework (JUnit/TestNG/PHPUnit/NUnit/RSpec/py.test)
2. Map your test cases to QC test cases. I described how I did this in detail by extending JUnit in these posts:
- Integrating JUnit tests with HP/Mercury Quality Center part 1
- Integrating JUnit tests with HP/Mercury Quality Center part 2
Note that this isn’t necessarily the way I’d do it now. Annotations are useful, but I think a mapping file is perhaps easier. Simply create a spreadsheet with the QC TestId in one column and the xUnit test name in another column. This is a little trickier with parameterized tests.
3. Parse the tests results from your test runner and update Quality Center using the OTA API (OTAClient.dll is installed with QC Explorer & can be downloaded from QC. Go to Help->Addins Page->HP Quality Center Client Side Setup Add-in)
I have a quick example of how to connect to Quality Center using OTAClient here:
Connecting to HP/Mercury Quality Center from a client side script
You can check out my sample QCIntegration project on GitHub:
http://github.com/fijiaaron/QCIntegration
I’m adding more details about integrating with Quality Center on One Shore.
Hi, I'm Aaron Evans. I am an independent software tester with 10+ years experience.
Hi Aaron,
Thanks a lot for this post. I have been working on the integration of selenium and quality center from the past few days but could not find anything that would help.Sure yours is the first post which I found very useful. Could you please explain this part of your post.
You can now have your junit test cases extend TestBase and get a csv report of test coverage.
public class MyTest extends TestBase {
@Test
@QCTestCases(covered = { “QC-TEST-1″, “QC-TEST-2″ }, related = { “QC-TEST-3″, “QC-TEST-4″, “QC-TEST-5″ })
public void testSomething() {
//implementation…
}
@Test
@QCTestCases(covered = { “QC-TEST-6″} })
public void testSomethingElse() {
//implementation…
}
}
By: jyothi on November 27, 2011
at 10:13 pm
That is just an example of using an annotation to identify which Quality Center test cases are covered in your JUnit test cases.
public class MyTest extends TestBase {
@Test
@QCTestCases(covered={"QC-TEST-1", "QC-TEST-2"}, related={"QC-TEST-3"})
public void testSomething() {
assertTrue(true);
}
}
For a clear example of what’s happening with a test case that looks like this:
public class MyTest extends TestBase {
@Test
@QCTestCases(covered={"QC-TEST-1", "QC-TEST-2"}, related={"QC-TEST-3"})
public void testSomething() {
assertTrue(true);
}
}
You can use reflection in the base class to get the annotations like this:
public class TestBase {
@Rule public TestName testName = new TestName();
QCTestCases qcTestCases;
@Before
public void getQCTestCoverage() {
try {
Method m = this.getClass().getMethod(testName.getMethodName());
if (m.isAnnotationPresent(QCTestCases.class)) {
qcTestCases = m.getAnnotation(QCTestCases.class);
}
} catch (SecurityException e) {
e.printStackTrace();
} catch (NoSuchMethodException e) {
e.printStackTrace();
}
}
@After
public void writeCoverageReport() {
StringBuilder result = new StringBuilder();
result.append(testName.getMethodName());
result.append(",");
for (String qcTestId : qcTestCases.covered()) {
result.append(qcTestId);
result.append(",");
}
System.out.println("qc tests covered: " + result);
}
}
It’s probably a bit unnecessarily complex, since “related” tests are not needed in most cases — I was using it purely for analysis, and if you have a 1:1 mapping you wouldn’t need to use arrays either, and your annotation interface could be as simple as this:
public @interface QCTestCase {
String name();
}
I’ve added the code you see here to the QCIntegration repository on github as well.
Of course, the next step is to get the test results in the csv file. That’s not detailed here, but I’ll work on demonstrating that another day.
By: fijiaaron on November 28, 2011
at 1:23 pm
Thanks in advance
By: jyothi on November 27, 2011
at 10:14 pm
Thank you Aaron. My TestBase class is generating qcCoverageReport.csv but it is not storing any logs in the file.
This is my log4j.properties file:
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern =%d{ABSOLUTE} %5p %c{1}:%L – %m%n
log4j.appender.stdout=org.apache.log4j.DailyRollingFileAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern =%5p (%F:%L) [%d] – %m%n
log4j.appender.stdout.File=C:\\junit\\qcCoverageReport.csv
log4j.rootLogger=INFO, stdout
Can you please tell me where the mistake is..?
Thanks,
Jyothi
By: jyothi on November 30, 2011
at 12:34 am
I’m using NLog, not Log4j
By: fijiaaron on November 30, 2011
at 2:58 pm
I am able to generate the log file now. :)
By: jyothi on November 30, 2011
at 3:30 am
[...] http://fijiaaron.wordpress.com/2011/06/01/integrating-junit-with-hp-quality-center-part-2/ http://fijiaaron.wordpress.com/2011/11/16/upload-seleniumjunit-test-results-to-quality-center/ [...]
By: Selenium QC integration summary « Fiji Ecuador Seattle Greece Montana on February 2, 2012
at 8:51 am
[...] JUnit tests with HP/Mercury Quality Center Integrating JUnit with HP Quality Center part 2 Upload Selenium/JUnit test results to Quality Center Updating test results in QC using the QC OTA APK explained Getting a QC test coverage report from [...]
By: Selenium QC integration update « Fiji Ecuador Seattle Greece Montana on February 2, 2012
at 8:58 am