As "Quality is built in, not added on.” effective test strategies should be based on performing the quality reviews (verification) in all SDLC phases with more attention to the early phases such as requirements and design.
2. 7 reasons why testing should start early in the SDLC
Reason 1:
Defects detected in the early phases of the SDLC are less
expensive to fix.
•2
3. 7 reasons why testing should start early in the SDLC
Reason 2:
Testing is usually conducted near the end of the project,
delays in the early SDLC phases usually happens and result
squeezing the testing phase duration, so early test is a
good solution as test team will get more time to test the
software without depending on the test phase duration
only.
•3
4. 7 reasons why testing should start early in the SDLC
Reason 3:
Studies have shown that most of the software defects
detected during the testing phase originate in the early
analysis phase.
•4
5. 10 reasons why testing should start early in the SDLC
Reason 4:
Early phases testing can give early indicators and flags
about the software fulfillment and quality.
•5
6. 7 reasons why testing should start early in the SDLC
Reason 5:
Management will not feel that testing is the bottleneck to
release.
•6
7. 7 reasons why testing should start early in the SDLC
Reason 6:
Testers will be more familiar and more knowledgeable
with the software as they are more involved in all phases
and not in testing phase only.
•7
8. 7 reasons why testing should start early in the SDLC
Reason 7:
Injecting testing activities in almost all phases will create
more ‘quality awareness’ and build ‘quality culture’ within
the organization.
•8
9. 7 reasons why testing should start early in the SDLC
Author:
Belal Raslan (Quality Consultant)
Email: Braslan@sq-partners.com
Twitter: @BelalRaslan
•9