This pages shows the integration between Jazz/RQM and Cucumber.
Cucumber is a tool for running automated acceptance tests written in a behavior-driven development (BDD) style
So What? Why would an organization use Jazz/RQM to start Cucumber?
Cucumber is a powerful test-execution engine. It does not MANAGE change in requirements, code or any
other activity needed for software delivery. This integration leverage the power
of Cucumber (and it's world) and the Jazz platform (and that world).
Having this two you benefit from the combination of both worlds.
You could state it in a table (not all pro- and cons- are listed here).
Less Good Not covered
Clear Language - BDD
Clear Language - BDD
Make note that the Test Management and Reporting goes beyond Cucumber, it covers many test execution tools including manual execution.
As a testmanager once said to me "I use Executable Specifications(*1) to bring people together!"
In combination wiht Rational you can bring more people together, and still keep control!
*1 - Or any other name you can give to this.
When setup the using of the technology is very simple:
Create Test Cases
Place your cucumber feature 'text' in the Test Case Design section
Assign the RQM-Testscript with the cucumber CMD-line to the Test Case
Figure: The RQM Test Case with the feature script.
Figure: The RQM Test Case Results.
Figure: The RQM Test Case Cucumber log (34_Cucumber.html).
Making use of the RQM/CLM environment one can create report using the RPE tool. This can reveal the fearture definitions in the Test Plan/Test Case listings.
A simple example is shown here. More elaborated reporting can be found on Comprehensive test plan reporting with RPE and RRDG.
I use the following rqmcucumber.bat. Make note that the CMD Line
does not have a Setup Java reference, the rqmcucumber.bat does.
That gives the option to have different Java versions in
different CMD executions.
rem Prepare clean environment
rem Set work directory
set WorkDir=C:\\PRJ\\RQM Extractor
rem Set common directory
if exist features goto continue
echo *** ERROR The features directory does not exists in %WorkDir% > %LogFile%
echo *** ERROR RQM Cucumber process aborted >> %LogFile%
rem Clean any previous generated files.
del /Q %FeatureFile%
del /Q %FeatureFile%.txt
del /Q %LogFile%
del /Q %CucumberResult%
echo Starting Cucumber %FeatureFile% > %LogFile%
echo Current date and time >> %LogFile%
date /T >> %LogFile%
time /T >> %LogFile%
echo Current Working directory >> %LogFile%
cd >> %LogFile%
rem Extract Test Case Design
rem Set Java
echo Extracting Test Case %qm_RQM_TESTCASE_WEBID% >> %LogFile%
java -jar RQMExtractor.jar -id=%qm_RQM_TESTCASE_WEBID% >> %LogFile%
rem Run the Cucumber engine
echo Executing Start: Cucumber %FeatureFile% --format html --out %CucumberResult% >> %LogFile%
call cucumber %FeatureFile% --format html --out %CucumberResult% 2>> %LogFile%
echo Executing End: Cucumber >> %LogFile%
rem Set Attachment Files and Exit
rem For easy access in the browser we add a .txt extension to the feature file
ren %FeatureFile% %FeatureFile%.txt
echo %FeatureFile%=%WorkDir%\\%FeatureFile%.txt >> %qm_AttachmentsFile%
echo %LogFile%=%WorkDir%\\%LogFile% >> %qm_AttachmentsFile%
echo %CucumberResult%=%WorkDir%\\%CucumberResult% >> %qm_AttachmentsFile%
rem Do not remove files. These are processed after closure of script!
Do not use the " in the %qm_AttachmentsFile% lines as stated in the documentation.
Make note that you can expand this script using --tags and --name arguments in the test-script!
Warning The Java definition must be added to the standard CMD Line Adapter starter script.
Setvars just defines the java location.
set JAVA_HOME=C:\Program Files (x86)\Java\jre7