Test Data Management
As a new important module of the Itedama application, I decide to dedicate a specific presentation about this new module.
This complete new module allow user to manage Test Design phase using one of the most important test techniques on functional testing : decision table.
This module is compliant to be used with Mercury Quality Center 9.0 using the Ms Excel add-in.
General Step Actions
The main scope of this sub-module is to manage test steps that are common on the application under test.
The user has to introduce a step description and a step expected result.
All the encoded general step actions will be further available while creating test cases.
Items describes as step can be like buttons, menu, links, common process actions...etc.
Using this way, all users will use the same language and step "way of description".
Test Case Template
As from now general steps are encoded, user can define a Test Template to use while creating test cases.
User can select either general step action or manually encode specific steps.
All steps are automatically incremented with a sequential name.
When a Test Template is created, user can retrieve it on the test case creation. In one click, all steps of the template will be added to the new Test Case.
Decision table Management
This is one of the most important part of the test design phase, setting up the decision values that will be tested.
According to the specifications of application under test, user will first define the structure of the decision table.
He/she will indicate all fields that will be used to define test values.
Once it is done, if will create for the selected decision table, all the values that will cover the specifications trying to reach the 100% testing coverage.
All the encoded values will be available while creating test cases and will be automatically formated with field names and corresponding values.
Test Case Definition
As this module is in line with Mercury Quality Center, the fields to encode are oriented to be used with the mandatory fields of QA Test Plan module.
User has to encode a Subject (tree on the Test Plan), test name, Description, partner and introduced release.
At this time user has several choices. He can load a previous encoded test template that will fill the test case with all the steps of the Test Template.
If the step "DECISION TABLE" is listed, the application will ask to select a decision table and test value to update on this step.
User can retrieve decision table test values and also insert update or delete steps of the test case.
Export Test Cases
When user has finished encoding test cases, he can by subject generate and export test cases on a formatted Excel file.
At this time, I manage the export to quality center test data using the Mercury Quality Center Ms Excel add-in.
When the Excel file is created, user has to open it, select all test cases and perform the export procedure available on menu "Tools - Export to Quality Center".
A refresh on quality center and all test cases are presents and usable.
Test Case Maintenance
If needed, user can modify the general parameters of each test case such as description, subject and introduced release.
All related step of the test case are also automatically updated.
Release Maintenance
Each new release, user has to re-encode test cases on a new Test Plan on Mercury Quality Center.
All test cases have to be updated too. User can select a new release (values are managed on the parameters of Itedama) and assign this new value to all test case.
This mean that all subject will be updated in the case of the root directory used on Test Plan contain the release name value.
Otherwise, user don't need to update the release and will simply reload Test Cases on a new domain - Project on Quality Center.
