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).
Greater consistency and repeatability: People have tendency to do the same task in a slightly different way even when they think they are repeating something exactly. A tool will exactly reproduce what it did before, so each time it is run the result is consistent.
*Objective assessment: If a person calculates a value from the software or incident reports, by mistake they may omit something, or their own one-sided preconceived judgments or convictions may lead them to interpret that data incorrectly. Using a tool means that subjective preconceived notion is removed and the assessment is more repeatable and consistently calculated. Examples include assessing the cyclomatic complexity or nesting levels of a component (which can be done by a static analysis tool), coverage (coverage measurement tool), system behavior (monitoring tools) and incident statistics (test management tool).
*Ease of access to information about tests or testing: Information presented visually is much easier for the human mind to understand and interpret. For example, a chart or graph is a better way to show information than a long list of numbers – this is why charts and graphs in spreadsheets are so useful. Special purpose tools give these features directly for the information they process. Examples include statistics and graphs about test progress (test execution or test management tool), incident rates (incident management or test management tool) and performance (performance testing tool).
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.
Risks include:
*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.
*People often make mistakes by underestimating the time, cost and effort for the initial introduction of a tool: Introducing something new into an organization is hardly straightforward. Once you purchase a tool, you want to have a number of people being able to use the tool in a way that will be beneficial. There will be some technical issues to overcome, but there will also be resistance from other people – both need to be handled in such a way that the tool will be of great success.
*People frequently miscalculate the time and effort needed to achieve significant and continuing benefits from the tool: Mostly in the initial phase when the tool is new to the people, they miscalculate the time and effort needed to achieve significant and continuing benefits from the tool. Just think back to the last time you tried something new for the very first time (learning to drive, riding a bike, skiing). Your first attempts were unlikely to be very good but with more experience and practice you became much better. Using a testing tool for the first time will not be your best use of the tool either. It takes time to develop ways of using the tool in order to achieve what is expected.
*Mostly people underestimate the effort required to maintain the test assets generated by the tool: Generally people underestimate the effort required to maintain the test assets generated by the tool. Because of the insufficient planning for maintenance of the assets that the tool produces there are chances that the tool might end up as ‘shelf-ware’, along with the previously listed risks.
People depend on the tool a lot (over-reliance on the tool): Since there are many benefits that can be gained by using tools to support testing like reduction of repetitive work, greater consistency and repeatability, etc. *people started to depend on the tool a lot. But the tools are just a software they can do only what they have been designed to do (at least a good quality tool can), but they cannot do everything. A tool can definitely help, but it cannot replace the intelligence needed to know how best to use it, and how to evaluate current and future uses of the tool. For example, a test execution tool does not replace the need for good test design and should not be used for every test – some tests are still better executed manually. A test that takes a very long time to automate and will not be run very often is better done manually.
If software were reliable, it would have no disadvantages.
Advantages: reliability and trustDisadvantages: expensive
What are the advantages and disadvantages of the close source software ?
what is the disadvantages of clinck software
re
what is the advantages of off the shelf software
what is the advantages of off the shelf software
NONE
Two advantages of custom written software are that the software is specific for the needs of the consumer, and the consumer owns the software after it is written for them. Two disadvantages are that this software often needs debugged, which can take hours, and the consumer does not get the credit for writing the software.
Navion is easy to use, very efficient and has no disadvantages.
Disadvantages; 1. You must learn the software. 2. The software will have bugs, so sometimes it will not work properly. The advantages far out-weigh the disadvantages.
1-It leads to software reusability. 2-It leads in readuction of production cost up to 85% and save production time upto 70%. 3-system reliability can be increased here.
Pi55 off.