- automatically get the new information.
- It's easy to filter and sort the information to view only what's needed.
- We can generate dynamic reports from the database to select exactly the
information we want, when we want it, to meet the specific needs of our software development and test process.
- If certain information must be kept private to certain individuals, the database can implement a security scheme that will restrict individual users' access to the data as appropriate.
- Most database products support a wide range of data-exchange formats. This means that data can be readily imported from or exported to other systems.
- The database supports multiple concurrent users.
- Storing all the information together means that we have only one area that we need to be concerned about backing up. When our database is backed up, we can be assured that all our information is safe.
The advantages of Web technology for client implementation include
- A well-designed Web form can ensure that data is collected consistently throughout the organization.
- By using "smart" data entry screens, data can be checked for errors before it is saved to the database.
- It helps team members to easily connect globally.
- It allows easy selection of data by use of pull-down menus, check boxes, and radio buttons.
- It exploits the incorporation of "value" fields to "hard-code" entries after they have been entered. This ensures repeatability and soft documentation of software test procedure inputs.
- A known template makes following standard operating procedures easy to follow.
- Placing testing information on our testing Web site will help remove all communication obstacles; everyone in the team will have the most recent information. This comes in handy when team members are from different locations. It even enables collaboration with different project partners.
A test management tool can help automate key processes in test definition, tracking, execution, and reporting.
Salient Features of Reengineered Test Management
Test design and procedure development
At the test design stage, testers will create a description of each test, document its scope and objective, and include any information that helps illustrate the purpose of a specific test such as requirements documents, functional specifications, etc.
During the test development phase, testers will document detailed test execution steps and define the expected results for each step. The test management system will help in defining and documenting test cases by providing standard Web-based, pre-formatted template forms with fields based on the product and component information for editing and creating test cases. These get posted to the centralized database. This enables standardization and consistency across the testing team. It will also help in linking to the requirements specification to ensure traceability and test coverage. The test case may have been created due to a known defect and gets an association created with that defect. We can define the sequence in which test cases should be executed. This may be based on functional dependencies or some other factors like risk and other priority.
To verify application functionality and usability, tests have to realistically emulate end-user behavior. To achieve this, test execution should follow predefined logic, such as running certain tests after other tests have passed, failed, or been completed. For example, a user logs into the system, enters a new order and then exits the system. To emulate this simple business process, it makes sense to run the tests following the exact same sequence: log in, insert order, log out. The execution logic rules should be set prior to executing the actual tests.
Once the test cases have been created, we can get them reviewed by required team members and customers. It