# Test management tool - (Optional)
why because : Helps in :
- Saving time in the creation and duplication of test scripts
-Staffing decisions accurately
-Testing process and implementation
- Maintaining documentation and implementation to meet the
requirements
- Taking corrective steps before the system goes live
- Tracking specific information about individual test scripts
- Getting updates on daily testing activities
- Record test results and produce statistical reports on test results
# Unit test tool -
Why because:
unit test must be performed by the programmers and each class implemented must have programmer-developed unit tests, for everything that "could possibly break". These tests are to be written during coding of the class, preferably right before implementing a given feature. Tests are run as frequently as possible during development, and all unit tests in the entire system must be running at 100% before any developer releases his code.
# functional/regression test tool -
If I adopt this tool then i can reduce risks and make the most of limited resources by implementing automated functional and regression testing of critical applications, whereby development and QA teams create reusable test assets that provide in-depth defect analysis and expedite resolution of defects.
Why because:
-It will ensure that the quality at every step of delivery
-It will fill the gap between the development and testing teams
-it will quickly identify and correct problems and cost- effective
# Load and stress tool -
Why because
It will help us to interpret the data, and point at the most likely performance problems.
# Bug tracking tool -(Optional)
Why because:
It is quite hard to keep track of what bugs have been raised, and which of them have been fixed. As well as automating this process, bug tracking tools make it extremely easy to analyze projects using metrics and reports
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment