Topic: Testing Testability

Message

   Testing Testability

Summary: 

Recently I overheard a conversation between a test analyst and a
business analyst about how a function should be tested. The response
from the business analyst was, "If it is not breaking the application,
it must be working fine!" Testing staff comes across such scenarios
where a part or functionality of the application under test is not
"testable." The tests they carry out are not conclusive enough to say
that the functionality is working as specified. In this week's article,
Ipsita Chatterjee defines testability and looks at the benefits of
incorporating it in the products. Also discussed are simple ways to
monitor the incorporation of this non-functional requirement in the
software development life cycle and a few industry myths about
testability.

What is Testability?  

Testability is a non-functional requirement important to the
testing team members and the users who are involved in user acceptance
testing. It can be defined as the property that measures the ease of
testing a piece of code or functionality, or a provision added in
software so that test plans and scripts can be executed systematically.

Why is Testability necessary?  

A typical software development lifecycle involves requirements
gathering, analysis, design, coding, testing, implementation, and
maintenance. A testable product ensures complete execution of the test
scripts. Assuming that good test coverage is applied, most of the
defects will be uncovered and fixed before the product is released.
This insures customers will report a minimum number of defects. A lot
of money is spent on supporting and maintaining a product after its
development. Testable products are easy and less costly to maintain.
The chances of achieving customer satisfaction with such products is
are much higher. Hence testability is an important attribute to the
maintainability of any software product. 

How is this attribute measured and monitored?  

Being able to test software, a piece of code or functionality, depends
on what the user can see and control, known as observability and
controllability. 

Observability enables a tester or user to see the external and internal
of the software. When a user receives the correct expected output, but
the internal or the background processes are not quite what was
specified in the requirements, defects are often found elsewhere. This
is more important in the case of unit and integration testing rather
than a simple black box testing. 

Controllability is a measure of how easily a tester or a user can
create difficult scenarios to test the software under extreme
circumstances. For example, behavior of an application cannot be tested
very easily when the hard disk is full or table overflow conditions
exist.

Author	Message
sudha Newbie Joined: 04Apr2007 Online Status: Offline Posts: 1	Topic: Testing Testability Posted: 04Apr2007 at 3:23am
	Testing Testability Summary: Recently I overheard a conversation between a test analyst and a business analyst about how a function should be tested. The response from the business analyst was, "If it is not breaking the application, it must be working fine!" Testing staff comes across such scenarios where a part or functionality of the application under test is not "testable." The tests they carry out are not conclusive enough to say that the functionality is working as specified. In this week's article, Ipsita Chatterjee defines testability and looks at the benefits of incorporating it in the products. Also discussed are simple ways to monitor the incorporation of this non-functional requirement in the software development life cycle and a few industry myths about testability. What is Testability? Testability is a non-functional requirement important to the testing team members and the users who are involved in user acceptance testing. It can be defined as the property that measures the ease of testing a piece of code or functionality, or a provision added in software so that test plans and scripts can be executed systematically. Why is Testability necessary? A typical software development lifecycle involves requirements gathering, analysis, design, coding, testing, implementation, and maintenance. A testable product ensures complete execution of the test scripts. Assuming that good test coverage is applied, most of the defects will be uncovered and fixed before the product is released. This insures customers will report a minimum number of defects. A lot of money is spent on supporting and maintaining a product after its development. Testable products are easy and less costly to maintain. The chances of achieving customer satisfaction with such products is are much higher. Hence testability is an important attribute to the maintainability of any software product. How is this attribute measured and monitored? Being able to test software, a piece of code or functionality, depends on what the user can see and control, known as observability and controllability. Observability enables a tester or user to see the external and internal of the software. When a user receives the correct expected output, but the internal or the background processes are not quite what was specified in the requirements, defects are often found elsewhere. This is more important in the case of unit and integration testing rather than a simple black box testing. Controllability is a measure of how easily a tester or a user can create difficult scenarios to test the software under extreme circumstances. For example, behavior of an application cannot be tested very easily when the hard disk is full or table overflow conditions exist. Post Resume: Click here to Upload your Resume & Apply for Jobs

	IP Logged


One Stop Testing Forum : Types Of Software Testing @ OneStopTesting : Unit Testing @ OneStopTesting