Software Testing Basics: Basic Techniques for
Testing the Software
The software development life cycle consists of the
following steps.
|
1. Planning |
|
2. Requirement analysis |
|
3. Design & Development |
|
4. Implementation |
|
5. Testing & Integration |
|
6. Evaluation |
|
7. Release |
| |
8. Support |
From the above, it can be seen that the Testing is one of
the major steps in the software development life cycle.
The purpose of testing is to find out the errors or mistakes
either in the software or in the coding. For example a C
language compiler points out the errors in the coding of any
software written using C language. Similarly the software
testing software points out errors in the software. Both the
developer and the software programmer or coder should have
knowledge of software testing basics.
The process of testing consists of unit testing, integration
testing, system testing, system integration testing, alpha
testing, beta testing and acceptance testing. The testing
methods are white box testing, grey box testing and black box
testing.
Now days the testing by manual means is being replaced by
automation wherein you use automated software for testing. Such
software is available in the market. You can install this
software on your computer and when applied to your software
under development you will get results immediately.
In earlier days, many companies were subcontracting the
software testing to outside companies. Nowadays the trend is
changing and the companies are developing their own software
for testing which will reduce the human effort. This is done to
reduce the extent of outsourcing. Some companies do partial
outsourcing.
There are a number of methods in which automated testing can
be conducted. For each of these methods individual disks are
available in the market and one can use any of these disks to
conduct test on the software and its code. Normally these disks
can be used for a number of years beyond which one can use this
as a platform for further development. The software testing
software has made life simple for both the developer and the
software programmer or coder.
The software testing basics consist of the basic testing of
the software or code. This is a relatively simple process and
every coder or developer is aware of it. As long as the
software continues to be valid the process of testing
continues.
In any software project management, software testing, and
software engineering, Verification and Validation (V&V) is
one of the most important steps in the software testing basics.
This can be defined as the process of checking that a software
system meets specifications and that it fulfils its intended
purpose. It is normally part of the software testing process of
a project.
Validation is the process of evaluating software during or
at the end of the development process to determine whether it
satisfies specified requirement. Verification is the process of
evaluating software to determine whether the products of a
given development phase satisfy the conditions imposed at the
start of that phase. Verification testing is the test to verify
the software or the code.
The software or the code is tested by applying the inputs
and the output is verified and compared to the specifications
submitted by the user. The purpose of testing is to get quality
assurance. Testing normally is done by splitting the software
into different modules.
Each module is tested independently and the final testing is
done on integrated software containing independent modules. The
modules testing are known as unit testing whereas the testing
of combination of modules is known as integration testing.
Understanding software testing basics is very important and
this solves much of the problem for the company. Validation and
verification of the software by using the software testing
basics is beneficial to the company.
|