For any system, there are several possible test cases, and yet, invariably, we have time to run only a few of them, which in turn are expected to find most of the defects in the software. We know from experience that this is simply not possible. Therefore, in order to increase the chances of finding defects, testing tools may be used. There are numerous testing tools, each with specific capabilities and test objectives.
The selection of the best testing tool for a particular development environment is a critical success factor for the testing activities. A testing tool should be considered based on the test objectives. As a general guideline, one must investigate the appropriateness of a testing tool when the manual process is inadequate. For example, if a system needs to be stress tested, a group of testers could simultaneously log on to the system and attempt to simulate peak loads, but this approach is not a practical solution, as it has many limitations. The performance cannot be measured precisely or repeatedly. Hence, a suitable load testing tool can be used to simulate several virtual users under controlled stress conditions to measure the performance more precisely.
One of the chief concerns while choosing a testing tool is the cost of the tool itself. Since software testing usually attracts the least budget in an organization, the testing tools developed by the Open Source community is highly popular.
The objective of this project is to provide a tutorial for test tools hosted by Open Source, which are most popular it its genre. At least one testing tool has been selected for each type of testing with a number of supportive languages; namely, Unit Testing Tools, Function Testing Tools, Performance Testing Tools and Stress Testing Tools.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment