LEVELS OF SOFTWARE TESTING

http://www.tuto rialspo int.co m/so ftware _te sting /le ve ls_o f_te sting .htm Co pyrig ht tuto rials po int.co m

T here are different levels during the process of T esting . In this chapter a brief description is provided about
these levels.

Levels of testing include the different methodolog ies that can be used while conducting Software T esting .
Following are the main levels of Software T esting :

Functional T esting .

Non-Functional T esting .

FUNCTIONAL TESTING
T his is a type of black box testing that is based on the specifications of the software that is to be tested. T he
application is tested by providing input and then the results are examined that need to conform to the functionality
it was intended for. Functional T esting of the software is conducted on a complete, integ rated system to evaluate
the system's compliance with its specified requirements.

T here are five steps that are involved when testing an application for functionality.

Steps Desc ription

I T he determination of the functionality that the intended application is meant to perform.

II T he creation of test data based on the specifications of the application.

III T he output based on the test data and the specifications of the application.

IV T he writing of T est Scenarios and the execution of test cases.

V T he comparison of actual and expected results based on the executed test cases.

An effective testing practice will see the above steps applied to the testing policies of every org anization and
hence it will make sure that the org anization maintains the strictest of standards when it comes to software quality.

Unit Testing
T his type of testing is performed by the developers before the setup is handed over to the testing team to
formally execute the test cases. Unit testing is performed by the respective developers on the individual units of
source code assig ned areas. T he developers use test data that is separate from the test data of the quality
assurance team.

T he g oal of unit testing is to isolate each part of the prog ram and show that individual parts are correct in terms of
requirements and functionality.

Limitations of Unit Testing

T esting cannot catch each and every bug in an application. It is impossible to evaluate every execution path in
every software application. T he same is the case with unit testing .

T here is a limit to the number of scenarios and test data that the developer can use to verify the source code. So
after he has exhausted all options there is no choice but to stop unit testing and merg e the code seg ment with
other units.

Integ ration Testing

T he testing of combined parts of an application to determine if they function correctly tog ether is Integ ration
testing . T here are two methods of doing Integ ration T esting Bottom-up Integ ration testing and T op Down
Integ ration testing .

S.N. Integ ration T esting Method

1 Bottom-up integ ration

T his testing beg ins with unit testing , followed by tests of prog ressively hig her-level combinations
of units called modules or builds.

2 T op-Down integ ration

T his testing , the hig hest-level modules are tested first and prog ressively lower-level modules
are tested after that.

In a comprehensive software development environment, bottom-up testing is usually done first, followed by top-
down testing . T he process concludes with multiple tests of the complete application, preferably in scenarios
desig ned to mimic those it will encounter in customers' computers, systems and network.

System Testing
T his is the next level in the testing and tests the system as a whole. Once all the components are integ rated, the
application as a whole is tested rig orously to see that it meets Quality Standards. T his type of testing is
performed by a specialized testing team.

System testing is so important because of the following reasons:

System T esting is the first step in the Software Development Life Cycle, where the application is tested as
a whole.

T he application is tested thoroug hly to verify that it meets the functional and technical specifications.

T he application is tested in an environment which is very close to the production environment where the
application will be deployed.

System T esting enables us to test, verify and validate both the business requirements as well as the
Applications Architecture.

Reg ression Testing

Whenever a chang e in a software application is made it is quite possible that other areas within the application
have been affected by this chang e. T o verify that a fixed bug hasn't resulted in another functionality or business
rule violation is Reg ression testing . T he intent of Reg ression testing is to ensure that a chang e, such as a bug fix
did not result in another fault being uncovered in the application.

Reg ression testing is so important because of the following reasons:

Minimize the g aps in testing when an application with chang es made has to be tested.

T esting the new chang es to verify that the chang e made did not affect any other area of the application.

Mitig ates Risks when reg ression testing is performed on the application.

T est coverag e is increased without compromising timelines.

Increase speed to market the product.

Acceptance Testing
T his is arg uably the most importance type of testing as it is conducted by the Quality Assurance T eam who will
g aug e whether the application meets the intended specifications and satisfies the client.s requirements. T he QA
team will have a set of pre written scenarios and T est Cases that will be used to test the application.

More ideas will be shared about the application and more tests can be performed on it to g aug e its accuracy and
the reasons why the project was initiated. Acceptance tests are not only intended to point out simple spelling
mistakes, cosmetic errors or Interface g aps, but also to point out any bug s in the application that will result in
system crashers or major errors in the application.

By performing acceptance tests on an application the testing team will deduce how the application will perform in
production. T here are also leg al and contractual requirements for acceptance of the system.

Alpha Testing
T his test is the first stag e of testing and will be performed among st the teams (developer and QA teams). Unit
testing , integ ration testing and system testing when combined are known as alpha testing . During this phase, the
following will be tested in the application:

Spelling Mistakes

Broken Links

Cloudy Directions

T he Application will be tested on machines with the lowest specification to test loading times and any
latency problems.

Beta Testing
T his test is performed after Alpha testing has been successfully performed. In beta testing a sample of the
intended audience tests the application. Beta testing is also known as pre-release testing . Beta test versions of
software are ideally distributed to a wide audience on the Web, partly to g ive the prog ram a "real-world" test
and partly to provide a preview of the next release. In this phase the audience will be testing the following :

Users will install, run the application and send their feedback to the project team.

T ypog raphical errors, confusing application flow, and even crashes.

Getting the feedback, the project team can fix the problems before releasing the software to the actual
users.

T he more issues you fix that solve real user problems, the hig her the quality of your application will be.

Having a hig her-quality application when you release to the g eneral public will increase customer
satisfaction.

NON-FUNCTIONAL TESTING
T his section is based upon the testing of the application from its non-functional attributes. Non-functional testing
of Software involves testing the Software from the requirements which are non functional in nature related but
important a well such as performance, security, user interface etc.

Some of the important and commonly used non-functional testing types are mentioned as follows:

Performance Testing
It is mostly used to identify any bottlenecks or performance issues rather than finding the bug s in software.
T here are different causes which contribute in lowering the performance of software:

Network delay.

Client side processing .

Database transaction processing .

Load balancing between servers.

Data rendering .

Performance testing is considered as one of the important and mandatory testing type in terms of following
aspects:
 Speed (i.e. Response T ime, data rendering and accessing )

Capacity

Stability

Scalability

It can be either qualitative or quantitative testing activity and can be divided into different sub types such as Load
testing and Stress testing .

Load Testing
A process of testing the behavior of the Software by applying maximum load in terms of Software accessing and
manipulating larg e input data. It can be done at both normal and peak load conditions. T his type of testing
identifies the maximum capacity of Software and its behavior at peak time.

Most of the time, Load testing is performed with the help of automated tools such as Load Runner, AppLoader,
IBM Rational Performance T ester, Apache JMeter, Silk Performer, Visual Studio Load T est etc.

Virtual users (VUsers) are defined in the automated testing tool and the script is executed to verify the Load
testing for the Software. T he quantity of users can be increased or decreased concurrently or incrementally
based upon the requirements.

Stress Testing
T his testing type includes the testing of Software behavior under abnormal conditions. T aking away the
resources, applying load beyond the actual load limit is Stress testing .

T he main intent is to test the Software by applying the load to the system and taking over the resources used by
the Software to identify the breaking point. T his testing can be performed by testing different scenarios such as:

Shutdown or restart of Network ports randomly.

T urning the database on or off.

Running different processes that consume resources such as CPU, Memory, server etc.

Usability Testing
T his section includes different concepts and definitions of Usability testing from Software point of view. It is a
black box technique and is used to identify any error(s) and improvements in the Software by observing the users
throug h their usag e and operation.

According to Nielsen, Usability can be defined in terms of five factors i.e. Efficiency of use, Learn-ability,
Memor-ability, Errors/safety, satisfaction. According to him the usability of the product will be g ood and the
system is usable if it possesses the above factors.

Nig el Bevan and Macleod considered that Usability is the quality requirement which can be measured as the
outcome of interactions with a computer system. T his requirement can be fulfilled and the end user will be
satisfied if the intended g oals are achieved effectively with the use of proper resources.

Molich in 2000 stated that user friendly system should fulfill the following five g oals i.e. Easy to Learn, Easy to
Remember, Efficient to Use, Satisfactory to Use and Easy to Understand.

In addition to different definitions of usability, there are some standards and quality models and methods which
define the usability in the form of attributes and sub attributes such as ISO-9126, ISO-9241-11, ISO-13407 and
IEEE std.610.12 etc.

UI vs Usability Testing
UI testing involves the testing of Graphical User Interface of the Software. T his testing ensures that the GUI
should be according to requirements in terms of color, alig nment, size and other properties.
On the other hand Usability testing ensures that a g ood and user friendly GUI is desig ned and is easy to use for
the end user. UI testing can be considered as a sub part of Usability testing .

Security Testing
Security testing involves the testing of Software in order to identify any flaws ad g aps from security and
vulnerability point of view. Following are the main aspects which Security testing should ensure:

Confidentiality.

Integ rity.

Authentication.

Availability.

Authorization.

Non-repudiation.

Software is secure ag ainst known and unknown vulnerabilities.

Software data is secure.

Software is according to all security reg ulations.

Input checking and validation.

SQL insertion attacks.

Injection flaws.

Session manag ement issues.

Cross-site scripting attacks.

Buffer overflows vulnerabilities.

Directory traversal attacks.

Portability Testing
Portability testing includes the testing of Software with intend that it should be re-useable and can be moved from
another Software as well. Following are the strateg ies that can be used for Portability testing .

T ransferred installed Software from one computer to another.

Building executable (.exe) to run the Software on different platforms.

Portability testing can be considered as one of the sub parts of System testing , as this testing type includes the
overall testing of Software with respect to its usag e over different environments. Computer Hardware,
Operating Systems and Browsers are the major focus of Portability testing . Following are some pre-conditions
for Portability testing :

Software should be desig ned and coded, keeping in mind Portability Requirements.

Unit testing has been performed on the associated components.

Integ ration testing has been performed.

T est environment has been established.