9. Test Management Concept In Digité Create Test Script Execute Test Event Create Test Cases Create Test Event Create Test Cases Test Case Failed Raise a Defect Yes Close Test Event No Test Script1 Test Script2 Test Case1 Test Case2 Test Case3 Test Case4 Test Case5 Test Event
10. Overview Test Management is a project specific module and you can access it from Project Workspace>>Test Management .
16. Adding a Test Script To create a Test Script, navigate to Test Management>>Test Scripts section.
17. Adding a Test Script Enter values in the mandatory fields and, if required in the optional fields.
18. Adding Test Units to a Test Script Click the Add Test Unit icon to add a test unit to the Test Script. Click the Copy Test Unit icon to copy the test unit with the same details.
20. Creating a Test Event Navigate to Test Management>> Test Event Section and click the Add Test Event icon.
21. Creating a Test Event Enter values in the mandatory fields, and if required in the optional fields.
22. Importing Test Scripts to a Test Event Click the Import Test Scripts icon to identify the test scripts which will be executed as a part of this Test Event.
23. Importing Test Scripts to a Test Event Select relevant test scripts from the list displayed. Click the Project list to import the test scripts from other projects.
24. Assigning the Test Event Click the Batch Schedule icon. Select the test scripts to be assigned and scheduled, other details, and click the Batch Schedule button.
25. Executing a Test Event To execute a Test Event, navigate to the ‘ Event Test Scripts’ section in a Test Event. Click the Test Script that you want to execute.
26. Executing a Test Event Mark the status of the test unit as Pass, Fail, Pending, or Not Applicable based on the actual result.
27. Executing a Test Event Click the ‘No linked Defect’ icon to link a defect with the failed test unit.
28. Executing a Test Event Click the ‘Link New defect’ icon to link a new defect. Click the ‘Link Existing defects’ icon to link an existing defect.
29. Executing a Test Event Once the defect is linked to the test unit the icon will be changed to ‘Linked Defects’ indicating that defect has been linked.
31. Test Management Reports To view Test Management reports, navigate to Project Monitoring>>Report List>> Test Reports.
32. Test Event Summary Report Select the appropriate parameters for generating the report.
33. Test Event Summary Report Test Event Summary Report shows a summary of the particular test event.
34. Test Event Detailed Report Test Event Detailed Report shows a detailed view of the particular test event.
35. Test Execution Summary Report The Test Execution Summary Report gives quick summary displaying count of test cases that are pending, passed, etc. You can even filter by owner and the executor.
Welcome to Digité’s Test Management Training . In this training session, I’ll walk you through the Test Management module of Digité.
This training module is intended for the Project Managers, Team Leads, Module Leads, Testers, and other users of Digité, who play a role in the Test Management process.
However, before undergoing this training I would like to suggest that you go through the Digité UI Introduction and Digité Common Systems Operations Training modules. Also, you should have a basic understanding about the Test Management process, such as a Test Case, Test Script, etc. You should also have the URL and an account setup for the Digité sandbox environment for hands-on sessions.
By the end of this training, you should be able to: 1. Understand the concept of Test management. 2.Understand how Test management process has been implemented in Digité. 3.Understand functionalities available under the Test Management module of Digité application and should be able to work with them.
Let’s get started with the Training.
Here is the list of Test management topics that we would be covering in this training session. To start with, we will first understand the concept of Test management. Then, we will have a look at Test Management Process in Digité. Finally, we will proceed with the implementation and working of Test management module in the Digité application.
Let’s understand what is Test management?
We all know that, Quality of any Software product depends on how well it has been tested. Test Management is basically a practice of organizing and controlling the process and artifacts required for the testing effort. The diagram describes the basic Test Management process. Test Management is a cyclic process that starts with the Test Planning Phase. Test planning phase basically addresses the questions of why, what, where, and when to test. The reason why a given test is created is called a test motivator (for example, a specific requirement must be validated). What should be tested is broken down into many test cases for a project. Where to test is answered by determining and documenting the needed software and hardware configurations. When to test is determined by tracking iterations (or cycles, or time period) to the testing. The Next Phase is the Test Design Phase where the overall design of the full test cycle is created. This addresses the question of how a functionality will be tested. This is where somewhat abstract test cases are developed into more detailed test steps, which in turn will become test scripts (either manual or automated). Test execution includes running the tests by assembling test scripts sequentially into a suite of test events. Test reporting is how the various results of the testing effort are analyzed and communicated. This is used to determine the current status of project testing, as well as the overall level of quality of the application or system.
The Test Management Module of Digité application allows teams to plan, develop, execute and assess all testing activities within their project. The Figure shows a general Test Management cycle that is followed in Digité. The first Step is the creation of Test Cases which are referred as Test Units in Digité. The second step is to logically group these Test Units into a Test Script. For example, grouping of all test units belonging to a single module can be grouped into one Test Script. Next, you need to identify the scripts and test units to be run and create a Test Event and schedule it. While executing a Test Event if a tester finds that a test unit has failed, there’s an option to link a defect with that Test Unit. This Defect is added to the main Defect repository.
To access the Test management module in Digité, navigate to your project workspace, on the left pane, select the Test management module. The Test management workspace appears.
Let’s now understand the Test management features in detail.
In Digité, Test Units are created to validate a requirement against a functionality. You can add a new test unit by clicking the Test Unit menu option, in the Test Management Module. Click the Add Test Unit icon. The Details page and the Workflow tab for the new Test Unit appears. You need not enter the Workflow details now as the Test Unit would be executed as a part of a Test Event. You can assign resources and schedule a batch of test units from the Test Event.
Enter appropriate details in all the mandatory fields of the Details tab. Name –Name for the test unit for easy identification. Priority – Priority for the test unit based on which you can schedule the test execution. Date Identified –Select or type the date when you are creating the test unit. Enter appropriate details in the optional fields, if required. Description –Type an appropriate description for easy identification. Release –Select the release, if you want to associate the test unit to the release you added. Pre-requisite – Pre-requisites to be fulfilled before executing the test unit that can include a navigation, action or some information. Input Data –Any specific data required to execute the test unit. Navigation –Steps the tester needs to navigate through the functionality. Validation –Steps to be followed to validate the Test Unit. Expected Result –The result that is expected after the tester performs the validation steps. Other read-only fields such as, Planned Effort, Workflow Queue, etc. are not significant here. Note that you can create custom fields to an eform other than the existing fields and use the Field Description icon to add field-related help.
After you save the test unit, you are returned to the Test Units List view. If you click the newly added test unit, the Details page appears by default. Additionally sections such as Traceability, Comments, Previous versions ,and Activity Log appears after saving the test unit. If configured at the eform level, the Attachment tab will appear. These sections will have the common functionality as explained in the Digité Common System Operations Training Module.
In Digité, you can create Test Scripts which are logically grouped test units. You can create a Test Script for every feature/functionality, where all the relevant test units can be grouped as Script Steps and sequenced in the order they need to be executed.
To create a test script, navigate to Test Management>>Test Script menu . Click the Add Test Script icon, a new test script with the Details and the Workflow tab appears. Again, you need not enter the Workflow details now as the Test Script would be executed as a part of a Test Event.
Enter appropriate details in all the mandatory fields of the Details tab. Name –Name for the test script for easy identification. Priority – Priority for the test script based on which you can schedule the test execution. Date Identified –Select or type the date when you created the test script. Enter appropriate details in the optional fields, if required. Description –Type an appropriate description for easy identification. Release –Select the release, if you want to associate the test unit to the release you added. Input/Pre-requisite – Pre-requisites to be fulfilled before executing the test unit that can include a navigation, an action, or specific data required to execute the test script. Other read-only fields such as, Planned Effort, Workflow Queue, etc. are not significant here. After you save the test script, you are returned to the Test Scripts List view. If you click the newly added test script, its Details page appears by default. Additionally, sections such as, Script Steps, Traceability, Comments, Previous Versions, and Activity Log appears after saving the Test Script. The Attachment tab will appear if the eform is configured. These sections will have the common functionality as explained in the Digité Common System Operations Training Module.
You can logically group the test units into test scripts and define the sequence of test execution in the Script Steps tab. Various useful features are provided in this section to organize the test units within the test script like reusing the existing test units, copying, adding, deleting or Re-sequencing the test units. To add a test unit, copy test units from the repository or reuse test units. Select the test script from the Test Script List view displayed by navigating to Test Management>>Test Scripts. The Reuse functionality adds test units from different releases within the project. When a Test unit fails in a test script and if it is used in other test scripts in the same event, its status automatically changes to ‘Blocked’ wherever it is reused in the test event. Thus, it is ensured that any failed test unit will not be executed again by some other executor. At the same time it also prevents a user to file a duplicate defect. The Copy Test Units functionality copies test units from the s ame or other projects you select. These will be independent instances of the copied test units and not linked. You can make any changes and rename the test units. To reuse test units, click the Script Steps tab in the selected Test Script. Click the Reuse Test Units icon. From the Link Test Units window, select the test units you want to reuse. You can select a release to filter test units for any specific release. Additionally, use the Advanced Search criteria to search relevant test units for the invoked test script. To copy test units to a Test Script, click Copy Test Units icon in the Scripts Steps tab. Select the project and the release from the list. Additionally, to select specific test units, click Advanced Search, and then enter the required information. Click Submit. The test units meeting the criteria are displayed existing in the selected project and release. Select the check boxes and click Copy. The Script Steps tab displays a list of reused and copied test units. To create new test units within a test script, Click the Add Test Unit icon in the Script Steps tab. These will be added to the test unit repository directly. You can even create new test units within a Test Script. Select the relevant test units from the list displayed. Click the Add Test Units icon to add a test unit to the Test Script.
Test Events are the final execution blocks of the Test Management Cycle in Digité. You need to add related test scripts that would assess a deliverable, or any new or existing functionality.
To create a new test event, navigate to the Test Management>>Test Events menu. Click the Add Test Event icon in the List view of the Test Events. A new Test Event with the Details and the Workflow tab appears. You can assign single or multiple testers for a Test event using the Batch Schedule feature for Event Test Scripts. Thus, you need not assign testers separately through the Workflow tab.
Enter appropriate details in all the mandatory fields of the Details tab. Name –Name for the Test Event for easy identification. Priority – Priority for the Test Event based on which you can schedule the test execution. Date Identified –Select or type the date when you created the Test event. Enter appropriate details in the optional fields, if required. Release –Select the release, if you want to associate the test unit to the release you added. Input/Pre-requisite – Pre-requisites to be fulfilled before executing the Test Unit that can include a navigation, an action, or specific data required to execute the test script. In the Description tab, type an appropriate description for the test event for easy identification. After you save the Test Event, you are returned to the Test Events List view. If you click the newly added test event, its Details page appears by default. Additionally sections such as Traceability, Comments, Previous versions, and Activity Log appears after saving the Test Unit. If configured at the eform level, the Attachments tab will appear. These sections will have the common functionality as explained in the Digité Common System Operations Training Module.
Other additional tabs are, Event Test Units and Event Test Scripts. You need to add test scripts in the Event Test Scripts for execution. To import the test scripts into a Test Event, navigate to the Event Test Scripts Tab and click the Import Test Scripts icon. The Import Test Scripts window displays a list of all the Test Scripts created in the existing project. You can select various available filters to filter down to specific test scripts by selecting Release, In Test Event, etc. If you select Yes in the In Test Event list, it lists the test scripts that are present in other test events of the selected project. If you select No, it lists the test scripts that are just created as independent test scripts and not imported into any test event.
Digité provides you an option of importing the test scripts not only from the executing project, but also from other projects. Click the Project list and select the relevant project. Note that, test scripts without the test units and test scripts already present in this Test Event can not be added to the Test Event and hence won’t be available in the list. Once you select the test scripts and click the Save button, the test scripts will be added to the Test Event and are available for execution.
Once the Test Event is created, the Project Manager or the Test Lead can assign them to the testers. Once the test scripts are imported, the QA manager needs to schedule the test scripts by assigning tentative dates for execution. The Batch schedule feature helps the manager in scheduling and assignment work. In the Event Test Scripts tab, select the test scripts to be assigned and scheduled. Select the Schedule Date, Owner and Executor for selected test scripts and click the Batch Schedule button. Accordingly, the owner, executor and schedule date will be displayed for the selected test scripts in the List view. The value of field ‘Scheduled Flag’ would now be set as ‘Completed’ indicating that the test scripts have been scheduled for execution. If required, you can change any of the scheduled values for an individual test by clicking the required test script. The Test Unit Execution window appears , displaying all the test units grouped under that test script. A similar ‘Batch Schedule’ icon is available in the window, which will let the user change the scheduled date, owner & executor for a specific test unit. If there are different values of ‘Date Schedule’ set for individual test units within the test script, the earlier of those dates would be displayed as the ‘Date Scheduled’, at the test script listing view of ‘Event Test Script’ section.
Now let’s look at the actual execution process. In the Event Test Scripts tab, by default the ‘Overall Status’ of all the Test Scripts will be marked as Pending. To execute a test event, click the test script to be executed. You can filter the test scripts by clicking the List Properties down arrow. From the Table View list, select the view for displaying the columns as set in the Table view. The list displays the Table views you created in the Test Script sub module and those that are made available for all team members in the project.
The Test Execution window displays the test units to be executed in this Test Script. To view test units with particular values, set the filter criteria in fields such as Owner, Test Status, etc. and then click Go. The Table view consists of views you created in the Test Unit sub module and those that are made available for all team members in the project. By default the unexecuted test units are marked as’ Pending’. To view the details of the particular test unit before execution, click the ID of a Test Unit. Validate the actual results with the expected behavior and mark the status of the Test unit as Pass, Fail, Pending, or Not Applicable in the Test Status list and fill in other details such as, Execution Date, Actual result, Comments, etc. The Test Unit cannot be applicable for any of the following reasons: 1. Test Unit has been imported from a external file or an existing Test script by erroneously. 2. Changes in requirements related to functionality or navigation make the test unit inapplicable. 3. Changes in the Testing scope for the release. Click Save to save the execution details. When a Test Unit fails in a test script and if it is reused in other test scripts in the same event, the linked test unit is automatically blocked. Based on the status of all the Test Units you executed, the overall status of Test Script changes to: • Pass: If all the Test Units in the Test Scripts have passed. • Fail: If even a single Test unit in the Test Script fails. The 'Not Applicable' status in the Test Status does not determine the overall status of Test Script. For instance, if there are 100 test units in a Test Script, out of which 99 have passed and one is Not Applicable, the overall status of the Test Script is considered as ‘Pass’. You can use the Batch Update feature where you need to enter the same values repetitively for selected test units. Select the Select All check box in the first column, or check boxes next to only those Test Units that you want to update. Click the Batch Update icon next to the Filter icon. The fields that you can update appear in the List Properties pane. Select the check boxes for the fields you want to update. Click the Batch Update button. The details are updated for the selected Test Units. Now, click Save.
Once you mark the status of the Test Unit as failed and click on the save button below, a new icon called ‘No Linked Defect’ is displayed. If required, you can link a defect to this failed test unit. Click the No Linked Defect icon and a new page to link a defect is displayed.
To link a new defect, click the ‘Link New Defect’ icon. (screen needs to be changed) The test unit can be linked to defects within the project or other projects . In the Defect Details window, from the Project list, select the project to which you want to add the defect. Enter the details and save. By default, the defect will be added to the current project. You can also link the existing defect if you know that defect already exists in the Defect repository. Click the 'Link Existing Defects' icon. In the Defect Details window, from the Project list, select the project, and then enter the details using which you want to search the defect. Select the defect from the search results and click Add Links.
The No Linked Defect icon now changes to the Linked Defects icon which indicates that a defect has been attached to the Failed Test Unit. When you have executed Test Script, you would want to view a summary of the test units that have been executed in the Test Script. The Test Unit Execution Summary can be viewed for a particular Test Event listing the Test Scripts with the total Test Units segregated into number of Test units that are passed, failed, blocked, pending and that are not applicable.
Now, let us go through the reports that are available for the Test Management module of Digité.
Digité provides you two Test reports to monitor the planning and execution of Test Events. To access these Test reports navigate to Project Monitoring>>Report List Tab Under the Test Report Section you will see two reports: 1.Test Event Summary Report, and 2.Test Event Detailed Report Let’s have a look at these reports in brief.
Click the Test Event Summary Report. Select the test event for which you want to generate the report. Select the Test Event and Test Executor. You need to enter the execution dates if you select Executed in Test Execution Details. Click the Go button below.
Based on the parameters you select in the Edit page, the ‘Test Event Summary Report ‘ displays the summary of your executed Test Event.
Similarly you can view the Test Event Detailed report which shows a detailed view of the particular test event. The Reports will be dealt in detail in the Digité Reports Training session.
With this, you have come to the end of training. By now, you should have become familiar with the Test Management module of Digité. To summarize, Test Management is the practice of planning and executing the Test Cases so as to improve the overall quality of software product. The Test Management module in Digité application helps in : 1.Creating test units to validate the application with input/output parameters. 2.Group relevant test units logically into Test Scripts, and then into a Test Event. 3.Schedule the Test Event and assign resources. 4. Execute the Test Scripts in the Test Event and log defects for the failed test cases. 5. It also helps in monitoring execution progress through various Test Management Reports.
![Target Audience ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)