What is Manual Testing?
Manual testing is a testing process that is carried out manually in order to find defects without the usage of tools or automation scripting.
A test plan document is prepared that acts as a guide to the testing process in order to have the complete test coverage.
Manual Testing Techniques
- Acceptance Testing
- White Box Testing
- Black Box Testing
- Unit Testing
- System Testing
- Integration Testing
-------------------------------
What is Acceptance Testing?
Acceptance testing, a testing technique performed to determine whether or not the software system has met the requirement specifications. The main purpose of this test is to evaluate the system's compliance with the business requirements and verify if it is has met the required criteria for delivery to end users.There are various forms of acceptance testing:
- User acceptance Testing
- Business acceptance Testing
- Alpha Testing
- Beta Testing
Acceptance Criteria
Acceptance criteria are defined on the basis of the following attributes- Functional Correctness and Completeness
- Data Integrity
- Data Conversion
- Usability
- Performance
- Timeliness
- Confidentiality and Availability
- Installability and Upgradability
- Scalability
- Documentation
Acceptance Test Plan - Attributes
The acceptance test activities are carried out in phases. Firstly, the basic tests are executed, and if the test results are satisfactory then the execution of more complex scenarios are carried out.The Acceptance test plan has the following attributes:
- Introduction
- Acceptance Test Category
- operation Environment
- Test case ID
- Test Title
- Test Objective
- Test Procedure
- Test Schedule
- Resources
The acceptance test activities are designed to reach at one of the conclusions:
1) Accept the system as delivered
2) Accept the system after the requested modifications have been made
3) Do not accept the system
Acceptance Test Report - Attributes
The Acceptance test Report has the following attributes:- Report Identifier
- Summary of Results
- Variations
- Recommendations
- Summary of To-DO List
What is User Acceptance Testing?
User acceptance testing, a testing methodology where the clients/end users involved in testing the product to validate the product against their requirements. It is performed at client location at developer's site.For industry such as medicine or aviation industry, contract and regulatory compliance testing and operational acceptance testing is also carried out as part of user acceptance testing.
UAT is context dependent and the UAT plans are prepared based on the requirements and NOT mandatory to execute all kinds of user acceptance tests and even coordinated and contributed by testing team.
Acceptance Criteria
Acceptance criteria are defined on the basis of the following attributes:- Functional Correctness and Completeness
- Data Integrity
- Data Conversion
- Usability
- Performance
- Timeliness
- Confidentiality and Availability
- Installability and Upgradability
- Scalability
- Documentation
Acceptance Test Plan - Attributes
The acceptance test activities are carried out in phases. Firstly the basic tests are executed and if the test results are satisfactory then the execution of more complex scenarios are carried out.The Acceptance test plan has the following attributes
- Introduction
- Acceptance Test Category
- operation Environment
- Test case ID
- Test Title
- Test Objective
- Test Procedure
- Test Schedule
- Resources
The acceptance test activities are designed to reach at one of the conclusions :
1) Accept the system as delivered
2) Accept the system after the requested modifications have been made
3) Do not accept the system
Acceptance Test Report - Attributes
The Acceptance test Report has the following attributes:- Report Identifier
- Summary of Results
- Variations
- Recommendations
- Summary of To-DO List
- Approval Decision
-----------------------------------
What is Alpha Testing?
Alpha testing takes place at the developer's site by the internal teams, before release to external customers. This testing is performed without the involvement of the development teams.
Alpha Testing - In SDLC
How do we run it?
In the first phase of alpha testing, the software is tested by in-house developers during which the goal is to catch bugs quickly.
In the second phase of alpha testing, the software is given to the software QA team for additional testing.
Alpha testing is often performed for Commercial off-the-shelf software (COTS) as a form of internal acceptance testing, before the beta testing is performed.
-----------------------------------
What is Beta Testing?
Beta testing also known as user testing takes place at the end users site by the end users to validate the usability, functionality, compatibility, and reliability testing.
Beta testing adds value to the software development life cycle as it allows the "real" customer an opportunity to provide inputs into the design, functionality, and usability of a product. These inputs are not only critical to the success of the product but also an investment into future products when the gathered data is managed effectively.
Beta Testing Dependencies
There are number of factors that depends on the success of beta testing:
- Test Cost
- Number of Test Participants
- Shipping
- Duration of Test
- Demographic coverage
No comments:
Post a Comment