The 11-step software testing process involves verifying requirements, design, code, and installation as well as validating that user needs are met. The key steps include: 1) Developing a test plan based on an assessment of the development status. 2) Testing requirements, design, code during construction, and software changes to find defects. 3) Executing tests, recording results, and reporting findings throughout the process. 4) Conducting acceptance testing with end users to validate software meets needs. The goal is to deliver high-quality, bug-free software through a rigorous process of verification and validation activities.

1. Eleven Step Testing Process
Created By :- Harshil Barot
admin@justwebworld.com
JustWebWorld.Com

2. What is Software Testing Process ??
Software Testing Process is a Find out the Maximum
Bugs and Errors From the Software or Product and Make
the Software
Bugs or Error Free.(Bugs/Errors/Defects)
First Five Steps :- Verifications
Remaining 4 For :- Validation
Results of both verification and validation
should be documented.

3. Validation is used to test the software in an executable mo
Both verification and validation will be used to test the
installation of the software as well as changes to the
software.
The strategy provides a road map that describes the steps
be taken, when, and how much effort, time, and resources
will be required

4. The Following Professionals are Involved in Testin
Of System and Software
1.Software Developer(Designers + Coders)
2.Software Tester(Test Engineers)
3.Project Lead/Manager
4.Software Quality Assurance
5.End User

5. Tasks
Software Developers Develop the Software
Software Tester Test the Software and Find out the Maxim
Bugs From the Software
Software Quality Assurance Responsible for Software Qua
He always try for the Improve the Software Quality

6. Verification and Validation
 Software testing is part of a broader group of
activities called verification and validation that
are involved in software quality assurance
 Verification (Are the algorithms coded
correctly?)
◦ The set of activities that ensure that software correctly
implements a specific function or algorithm
◦ (Done By Developer)
 Validation (Does it meet user requirements?)
◦ The set of activities that ensure that the software that
has been built is traceable to customer requirements

7. Why Software Testing?
Without Software Testing Process,
1) The software has poor quality.
2) The software may contain the critical error or
bug.
3) The cost of error or bug may be too high.

8. Not Only Build Software
+
Robust, Powerful and Perfect Software
(Good Designs)
(Good Performance)
(Remove Unnecessary Code)
(User Friendly Software)
(Improve Software Quality)

9. 11 Steps For Software Testing Proces
Step 1: Assess Development Plan and Status
Step 2: Develop the Test Plan
Step 3: Test Software Requirements
Step 4: Test Software Design
Step 5: Program (Build) Phase Testing
Step 6: Execute and Record Results
Step 7: Acceptance Test
Step 8: Report Test Results
Step 9: The Software Installation
Step 10: Test Software Changes
Step 11: Evaluate Test Effectiveness

10. Step 1: Assess Development Plan and
Status
This first step is a prerequisite to building the VV&T Plan
used to evaluate the implemented software solution.
During this step, testers challenge the completeness
and correctness of the development plan. Based on
the extensiveness and completeness of the Project Plan
the testers can estimate the
amount of resources they will need to test the

11. Step 2: Develop the Test Plan
Forming the plan for testing will follow the same pattern as
any software planning process.
The structure of all plans should be the same, but the
content will vary based on the degree of risk the testers
perceive as associated with the software being developed.

12. Step 3: Test Software Requirements
Incomplete, inaccurate, or inconsistent requirements
lead to most software failures.
The inability to get requirements right during the
requirements gathering phase can also increase the
cost of implementation significantly.
Testers, through verification, must determine that the
requirements are accurate , complete, and they do not
conflict with one another.

13. Step 4: Test Software Design
This step tests both external and internal design
primarily through verification techniques. The
testers are concerned that the design will achieve
the objectives of the requirements, as well as the
design being effective and efficient on the
designated hardware.

14. Step 5: Program (Build) Phase Testing
The method chosen to build the software from the
internal
design document will determine the type and
extensiveness of tests needed.
As the construction becomes more automated, less
testing will be required during this phase.
However, if software is constructed using the
waterfall process, it is subject to error and should be
verified.
Experience has shown that it is significantly cheaper to
identify defects during the construction phase, than
through dynamic testing during the test execution step.

15. Step 6: Execute and Record Results
This involves the testing of code in a dynamic state.
The approach, methods, and tools specified in the test
plan will be used to validate that the executable code
in fact meets the stated software requirements,
and the structural specifications of the design.

16. Step 7: Acceptance Test
Acceptance testing enables users to evaluate the
applicability and usability of the software in
performing their day-to-day job functions.
This tests what the user believes the software
should perform, as opposed to what the
documented requirements state the software should
perform.
Acceptance Tests occurs at the time of Software or
App.
Installation.

17. Step 8: Report Test Results
Test reporting is a continuous process. It may be bo
oral and written. It is important that defects and
concerns be reported to the
appropriate parties as early as possible, so that
corrections can be made at the lowest possible cost.

18. Step 9: The Software
Installation
Once the test team has confirmed that the software is
ready for production use,
the ability to execute that software in a production
environment should be tested. This tests the
interface to operating software, related software,
and operating Procedures.

19. Step 10: Test Software Changes
While this is shown as Step 10, in the context of
performing maintenance after the software is
implemented, the concept is also applicable to
changes throughout the implementation process.
Whenever requirements change, the test plan must
change, and the impact of that change on software
systems must be
tested and evaluated.
Regression Testing :- At the time of Software Changes.

20. Step 11: Evaluate Test Effectiveness
Testing improvement can best be achieved by
evaluating the effectiveness of testing at the end of
each software test assignment. While this assessment
is primarily performed by the testers, it should involve the
developers, users of the software, and quality assurance
professionals if the function exists in the IT
organization.

21. Missions of Test Groups Can Vary
 Find defects
 Maximize bug count
 Block premature product releases
 Help managers make ship / no-ship decisions
 Assess quality
 Minimize technical support costs
 Conform to regulations
 Minimize safety-related lawsuit risk
 Assess conformance to specification
 Find safe scenarios for use of the product (find
ways to get it to work, in spite of the bugs)
 Verify correctness of the product
 Assure quality

22. After Testing Time to Launch the Software into
Market
Get Certify Secure Software
Get Authentication Certification
SSL Certificates powered by VeriSign

23. JustWebWorld.Com

24. JustWebWorld.Com