The features of test management tools are given below. Some tools will provide all of these features; others may provide one or more of the features. [Read more…]
One of the ways to do a proof-of-concept is to have a pilot project as the first thing done with a new tool. This will use the tool on a small scale, with sufficient time to explore different ways in which it can be used. Objectives should be set for the pilot in order to accomplish what is needed within the current organizational context. [Read more…]
While introducing the tool in the organization it must match a need within the organization, and solve that need in a way that is both effective and efficient. The tool should help in building the strengths of the organization and should also address its weaknesses. The organization needs to be ready for the changes that will come along with the new tool.
If the current testing practices are not good enough and the organization is not mature, then it is always recommended to improve testing practices first rather than to try to find tools to support poor practices. Automating chaos just gives faster chaos! [Read more…]
Although there are many benefits that can be achieved by using tools to support testing activities, but there are also many risks that are associated with it when tool support for testing is introduced and used.
- Unrealistic expectations from the tool: Unrealistic expectations may be one of the greatest risks to success with tools. The tools are just software and we all know that there are many problems associated with any kind of software. It is very important to have clear and realistic objectives for what the tool can do. [Read more…]
There are many benefits that can be gained by using tools to support testing. They are:
- Reduction of repetitive work: Repetitive work is very boring if it is done manually. People tend to make mistakes when doing the same task over and over. Examples of this type of repetitive work include running regression tests, entering the same test data again and again (can be done by a test execution tool), checking against coding standards (which can be done by a static analysis tool) or creating a specific test database (which can be done by a test data preparation tool). [Read more…]
Monitoring tools are used to continuously keep track of the status of the system in use, in order to have the earliest warning of failures, defects or problems and to improve them. [Read more…]
Performance testing tools are basically for system level testing, to see whether or not the system will stand up to a high volume of usage. A load testing is to check that the system can handle its expected number of transactions.
A volume testing is basically to check that the system can handle a large amount of data, e.g. many fields in a record, many records in a file, etc. A stress testing is one that goes beyond the normal expected usage of the system (to see what would happen outside its design expectations), with respect to load or volume. [Read more…]
Dynamic analysis tools are ‘dynamic’ because they require the code to be in a running state. They are ‘analysis’ rather than ‘testing’ tools because they analyze what is happening ‘behind the scenes’ that is in the code while the software is running (whether being executed with test cases or being used in operation). [Read more…]
There are many tools that protect systems from external attack. Like firewall, this is very important for any system.
Security testing tools can be used to test security of the system by trying to break it or by hacking it. The attacks may focus on the network, the support software, the application code or the underlying database. [Read more…]
These tools are mostly used by developers.
Coverage tools helps in checking that how thoroughly the testing has been done. [Read more…]