Project 1 - V&V SW Analysis - I
Black Box testing:
A method of testing that tests for functionality of the system without looking into the internal implementation/structure of the system.
The method which tester selects a function and gives input value to examine its functionality, and checks whether the function is giving the expected output or not if the function produces the correct output, then it is passed in testing, otherwise failed. The test team report reports the result to the development team and then tests the next function. After completing the testing of all functions if there are severe problem then it is given back to the development team for correction.
Test Plan:
Test Plan is a detailed documentation that consist of all future testing-related activities. It is prepared at the project level and in general, it defines work products to be tested, how they will be tested, and test type distribution among the testers. Before starting testing there will be a test manager who will be preparing a test plan. The Test manager plays main role for the successful test plan for execution process.
Importance of Test of Plan:
- The test Plan acts as the guide while doing the test.
- It says the Out-of-scope functionalities
- Determines the time, cost and effort
- Perfect schedule for the Test process.
- It is used as reference for the future purpose also and similar projects in future.
Components of the Test Plan:
1.Objective: It describes the illustrate of the test that is ,what are we going to in Test
like features-functionalities and non-functionalities and a making the software from the bug free software.
2.Scope of Testing: The scope of testing illustrates the Test efforts and Test cost
And divided into two parts
- In-scope: Feature that fall under the scope to be tested.
- Out-scope: Feature that do not fall under the scope to be tested.
3.Schedule of Test: The Schedule of the test is mainly says that when the test gets completed (on what date) and end date with respect to milestones planned.
4.Assumptions: 1. Assumptions of the Test
- Highly important things like proper knowledge transfer from the development team and resources for the Test department.
5.Risks: Risks are related to the availability of resources, availability of tests environment (test setups), technical knowledge of the team, etc.
6.Mitigation/Contingency plans: Contingency plans related to stabilizing and addressing risks in a structured fashion.
7.Roles And Responsibilities: All the roles and responsibility of every member in a particular testing team has to be recorded.
8.Test Methodology: The methods that are going to be used for testing depend on application to application. The testing methodology is decided based on the feature and application requirements. Since the testing terms are not standard, one should define what kind of testing
9.Test Approach: Test approach specifying the test approach to implement testing using test
Methodology (Analyze the prerequisites, Clarify SW acceptance criteria outline the test approach to the QA Management team, define and identify the approach to test execution).
10.Test Criteria:
Entry Criteria: The criteria that shall be met before we start executing a test case. Predefined set of conditions that shall be met.
Exit Criteria: The Criteria that shall be fulfilled to complete the SW testing life cycle (STLC).
11.Test Environment: It is the environment which the testing team will use the list of hardware and software, while testing the application, the things which are said to be tested will be written under this section. The installation of software is also checked under this.
12.Defect Tracking: Illustrate the tracking to bugs reported during various phases of SW testing (E.g.: Using JIRA)
Normally, a link to JIRA shall be provided.
13.Effort Estimation: Illustrate a detailed estimation of the effort required by the of the effort required by the test engineers in the team to carry out the testing activity.
14.Test Automation: Illustrate the required automation for the features that are tested manually , the scripting language used, link to the scripts, etc.
15.Test Deliverables: Illustrates a detailed list of all the test deliverables that will be an output of the activity.
Test Plan to Test features of a new mobile phone:
if (owner switch on the phone)
{
Company Logo at the center of the screen;
}
else if (customer press the power button)
{
Open the apps in the grid;
}
else if (owner power on the phone)
{
Shows call the phone icon in the first position at the bottom;
}
else if (owner power on the phone)
{
Shows Dictionary icon in the second position at the bottom;
}
else if (owner click on call the phone icon)
{
Contacts appear in chronological order;
}
else if (owner click on Dictionary icon)
{
The search bar appears at the center;
}
else if (owner long-press power on button)
{
Displays Good-bye and gets switched off;
}
else if (owner phone font)
{
Always in calibri with the size of 12;
}
else if (touch responsive)
{
Always need UI to be touch responsive;
}
else (customer required no hard buttons)
{
Touch screen sensitive;
}