Release testing and User testing

2. Presented By:
Tariq Ahmad 20-ARID-4421
And my partner name is
M.Talha 20-ARID-4404

3. Topic:
 Release testing
 User testing

4.  Introduction
 What is testing?
 Verification
 Validation
 Difference between Verification and Validation
 Stages of testing
 Development testing
 Release testing
 User testing
 Types of user testing
 Principal of Software testing
 Benefits of testing
Content

5. Introduction
 Testing is the process of exercising a program with the specific intent of
finding errors prior to delivery to the end user.
 When you test software , you execute a program using artificial data.
 You check the results of the test run for errors, anomalies or information
about the program’s non-functional attributes.
 Can reveal the presence of errors NOT their absence.
 Testing is part of a more general verification and validation process, which
also includes static validation techniques.

7. Testing is the process of executing a
program with the intention of finding
errors.

8. Verification
 Verification is the process to make sure product satisfies the conditions
imposed at the start of the development phase.
 To make sure the product behaves the way we want it to.

9. Validation
 Validation is the process to make sure the product satisfies the specified
requirements at the end development phase.
 To make sure that the product is built as per customer requirements.

10. Difference between verification and
validation
Verification Validation
• Check whether the software
conforms to specification
• Its does not involve executing the
code
• It is human based checking of
document and files
• Verification is done by development
team to provide that the software
is as per the specification
• Check whether the software meet
the customer requirements.
• Its always involves executing the
code
• Its computer based execution of
program
• Validation is carried out with the
involvement of client and testing
team.

11. Stages of testing

12.  Development testing
 Release testing
 User testing

13. Development Testing
 Development testing includes all testing activities that are carried
out by the team developing the system.
 Unit testing
 Component testing
 System testing

14. Release testing
 Release testing refers to coding practices and test strategies that give teams
confidence that a software release candidate is ready for users.
 Release testing aims to find and eliminate errors and bugs from a software release so
that it can be released to users.

16. User testing
 User or customer testing is a stage in the testing process in which users or
customer provide input and advice on system testing.
 User testing is essential, even when comprehensive system and release
testing have been carried out.

17. Types of user testing
Beta Testing
Acceptance Testing
Alpha testing

18. Alpha testing
To define simply it is before releasing the product , means it is something which
happens on developer site.
It is after the all other types of developer side testing means unit testing integration
testing etc.
It can be any black box or white box depends on the requirements.
Special lab environment and simulation of actual environment is required for this
testing.

20. Beta testing
At is after the releasing of the project/product, it is not some thing what happens at
developer side.
It is something what happens only on user side.
It is always black box testing, because you do not give access to user on your program
files and white box tesing is something which happens on the code so white box is not
possible at beta testing stage.
User test the actual product and give feedback, to make the creations.

21. Unit Testing
Integration
testing
System
Testing
Acceptance
Testing

22. Acceptance testing
Acceptance testing is level of software testing
where a system is tested for acceptability.

23. Acceptance Testing

25. Acceptance testing process

26. Principal of software testing
Testing should be based on use requirements.
Time & resources are limited.
Impossible to test everything
Use effective resources to test
Test planning should be done early
Testing should begin at module
Done by an independent party
Keep s/w static during test
Documents test case and result

27. Benefits of testing
Find problems early
Facilitates change
Simplifies integration
Documentation
Design

28. Conclusion
Software testing is the activity that executes software with an intention of finding
errors in it.
Software testing can provide independent view of the software to allow the business
to appreciate and understand the risk of software implementation.

29. .
Any question ?

30. Thank you for your
consideration