Validation Phases !!!!
Printed From: One Stop Testing
Category: Software Testing @ OneStopTesting
Forum Name: Beginners @ OneStopTesting
Forum Discription: New to the Club...!!! Don't Worry, We are here for you...!!! Learn the very basics of Software Testing and other pertinent Informations.
URL: http://forum.onestoptesting.com/forum_posts.asp?TID=2772
Printed Date: 08Feb2025 at 4:09am
Topic: Validation Phases !!!!
Posted By: tanushree
Subject: Validation Phases !!!!
Date Posted: 11Oct2007 at 12:19am
Validation Phases
Unit Testing
In
the V-model of software development, unit testing implies the first
stage of dynamic testing process. According to software development
expert Barry Boehm, a fault discovered and corrected in the unit
testing phase is more than a hundred times cheaper than if it is done
after delivery to the customer.
It involves analysis of the
written code with the intention of eliminating errors. It also verifies
that the codes are efficient and adheres to the adopted coding
standards. Testing is usually white box. It is done using the Unit test
design prepared during the module design phase. This may be carried out
by software testers, software developers or both.
Integration Testing
In
integration testing the separate modules will be tested together expose
faults in the interfaces and in the interaction between integrated
components. Testing is usually black box as the code is not directly
checked for errors. It is done using the integration test design
prepared during the architecture design phase. Integration testing is
generally conducted by software testers.
System Testing
System
testing will compare the system specifications against the actual
system. The system test design derived from the system design documents
and is used in this phase. Sometimes system testing is automated using
testing tools. Once all the modules are integrated several errors may
arise. Testing done at this stage is called system testing.
User Acceptance Testing
Acceptance
Testing checks the system against the requirements of the user. It uses
black box testing using real data, real people and real documents to
ensure ease of use and functionality of systems. Users who understand
the business functions run the tests as given in the acceptance test
plans, including installation and Online help. Hard copies of user
documentation are also being reviewed for usability and accuracy. The
testers formally document the results of each test, and provide error
reports, correction requests to the developers.
|
|