Professional Documents
Culture Documents
Testing Tools & Measurement: Unit 5 (12 Marks)
Testing Tools & Measurement: Unit 5 (12 Marks)
Unit 5
(12 Marks)
Benefits:-
4. Efficient & consistency testing
5. Better quality software
6. It is cheaper ,faster & more reliable.
1. Save Time /Speed: Due to advanced computing facilities, automation test tools prevail in
speed of processing the tests. Automation saves time as software can execute test cases
faster than human.
2. Reduces the tester’s involvement in executing tests: It relieves the testers to do some other
work.
3. Simulated Testing : Automated tools can create many concurrent virtual users/data and
effectively test the project in the test environment before releasing the product.
4. Test case design : Automated tools can be used to design test cases also through
automation, better coverage can be guaranteed than if done manually.
5. Reusable : The automated tests can be reused on different versions of the software, even if
the interface changes.
6. Avoids human mistakes : Manually executing the test cases may incorporate errors. But this
can be avoided in automation testing.
7. Internal Testing : Testing may require testing for memory leakage or checking the coverage
of testing. Automation can done this easily.
8. Cost Reduction : If testing time increases cost of the software also increases. Due to testing
tools time and therefore cost is reduced.
RAISONI GROUP OF INSTITUTIONS
Disadvantages of Using Tools
3. Training/skills : While test tools require plenty of training, very few vendors provide
the training to the required level. Organization level training is needed to deploy the
test tools, as the user of the test suite are not only the test team but also the
development team and other areas like configuration management.
4. Management aspects : A test tool increases the system requirement and requires the
hardware and software to be upgraded. This increases the cost of the already-
expensive test tool.
METRICS :
1. A Metric is a quantitative measure of the degree to which a system, system component,
or process possesses a given attribute. Metrics can be defined as STANDARDS OF
MEASUREMENT.
2. Software Metrics are used to measure the quality of the project.
3. Metric is a unit used for describing an attribute. Metric is a scale for measurement.
4. A Metric is a measurement of the degree that any attribute belongs to a system,
product or process.
5. For example the number of errors per person hours would be a metric. Thus, software
measurement gives rise to software metrics.
1. Process metrics
• These characteristics can be used to improve the development & maintenance activities of the
software.
• The process metrics are those metrics which are concerned with SDLC.
2. Product metrics
• Describes the characteristics of the product such as size, complexity, design feature,performance
& quality level.
3. Project metrics
• Describes the project characteristics & execution.
• These are more relevant to a project team.
• Defect density:-
Refers to number of imperfections per:- Lines of code , Function definitions, Lines on input screen.
• Customer problem
is a measure of problems customers have encountered with the product over the total usage of the product.
Measurement :
1. A measurement is an indication of the size, quantity, amount or dimension of a
particular attribute of a product or process.
2. For example : The number of errors in a system is a measurement.
1) Coupling Metrics:-
• Coupling relation increase complexity, reduce encapsulation, potential reuse, & limit understanding
& maintainability.
• Coupling measures requires information about attributes usage & method invocations of other class.
2)Cohesion Metrics:-
• Cohesion is the measure of the degree to which the elements of a module are functionally related.
• Cohesion measures requires information about attributes usage & method invocations within a class.
3) Inheritance Metrics:-
• Inheritance measures requires information about ancestors & descendants of a class.
4) Size metrics:-
• It indicates the length of a class in terms of lines of source code & methods used in the class.
• If a class has a large number of methods with greater complexity then more test cases will be
required to test that class.