11.What Is The Difference Between Master Test Plan And Test Plan?
The difference between Master Plan and Test Plan can be described using following points.
1.Master Test Plan contains all the test scenarios and risks prone areas of the application. Whereas, Test Plan document contains test cases corresponding to test scenarios.
2. Master Test Plan captures each and every test to be run during the overall development of application whereas test plan describes the scope, approach, resources and schedule of performing the test.
3. MTP includes test scenarios to be executed in all the phases of testing that run during the complete life cycle of the application development. Whereas, a separate Test Plan exists for each phase of testing like Unit, Functional, and System which contains the test cases related to that type only.
4. Only for big projects, we need a Master Test Plan which requires execution in all phases of testing. However, preparing a basic Test Plan is enough for small projects.
12.What Are The Different Types Of Software Testing?
Following is the list of various testing types used by manual testers.
- Unit testing
- Integration testing
- Regression testing
- Shakeout testing
- Smoke testing
- Functional testing
- Performance testing
- Load testing
- stress testing
- Endurance testing
- White box and Black box testing
- Alpha and Beta testing
- System testing
13.What is White Box Testing?
White Box Testing is also called as Glass Box, Clear Box, and Structural Testing. It is based on applications internal code structure. In white-box testing, an internal perspective of the system, as well as programming skills, are used to design test cases. This testing usually was done at the unit level.
14.What is Black Box Testing?
Black Box Testing is a software testing method in which testers evaluate the functionality of the software under test without looking at the internal code structure. This can be applied to every level of software testing such as Unit, Integration, System and Acceptance Testing.
15.What is Positive and Negative Testing?
Positive Testing: It is to determine what system supposed to do. It helps to check whether the application is justifying the requirements or not.
Negative Testing:It is to determine what system not supposed to do. It helps to find the defects from the software.
SOFTWATE TESTING
Weekend / Weekday Batch
16.What Is Alpha And Beta Testing?
Alpha testing: is performed by the IN-House developers. After alpha testing the software is handed over to software QA team, for additional testing in an environment that is similar to the client environment.
Beta testing: beta testing becomes active. It is performed by end user. So that they can make sure that the product is bug free or working as per the requirement. IN-house developers and software QA team perform alpha testing. The public, a few select prospective customers or the general public performs beta testing.
17.What Is Agile Testing?
Agile Testing means to quickly validation of the client requirements and make the application of good quality user interface. When the build is released to the testing team, testing of the application is started to find the bugs. As a Tester, we need to focus on the customer or end user requirements. We put the efforts to deliver the quality product in spite of short time frame which will further help in reducing the cost of development and test feedbacks will be implemented in the code which will avoid the defects coming from the end user.
18.Explain Bug Life Cycle.
- The bug is assigned to development project manager who will analyze the bug. He will check whether it is a valid defect. If not a valid bug is rejected then the status is REJECTED.
- If not, next the defect is checked whether it is in scope. When a bug is not part of the current release. Such defects are POSTPONED
- Now, Tester checks whether a similar defect was raised earlier. If yes defect is assigned a status DUPLICATE
- When a bug is assigned to the developer. During this stage, bug is assigned a status IN-PROGRESS
- Once a code is fixed. A defect is assigned a status FIXED
- Next, the tester will re-test the code. In case the test case passes the defect is CLOSED
- If the test case fails again the bug is RE-OPENED and assigned to the developer. That’s all to Bug Life Cycle.
19.Explain User Acceptance Testing.
User Acceptance Testing (UAT) is performed by the end users on the applications before accepting the application.
Alpha testing: is performed by the IN-House developers. After alpha testing the software is handed for the Beta testing phase, for additional testing in an environment that is similar to the client environment.
Beta testing: is performed by the end user. So that they can make sure that the product is bug free or working as per the requirement. IN-house developers and software QA team perform alpha testing. The public, a few select prospective customers or the general public performs beta testing.
Gamma Testing: Gamma Testing is done when the software is ready for release with specified requirements. This testing is done directly by skipping all the in-house testing activities.
20.What is Test Scenario?
Test Scenario gives the idea of what we have to test. Test Scenario is like a high-level test case.
