Project 1 - V&V SW Analysis - I
TEST PLAN
A test plan is a detailed document which describes software testing areas and activities.
BLACK BOX TESTING
Black-box testing is a method of software testing that examines the functionality of an application without peering into its internal structures or workings.Black Box Testing mainly focuses on input and output of software applications and it is entirely based on software requirements and specifications.
Components Of A Plan Document
| Items in a Test Plan Template | What do they contain? |
|---|---|
| Scope => | Test Scenarios/Test objectives that will be validated. |
| Out of scope => | Enhanced clarity on what we are not going to cover |
| Assumptions => | All the conditions that need to hold true for us to be able to proceed successfully |
| Schedules => | Test Scenario prep |
| Test Documentation- test cases/test data/setting up environment | |
| Test Execution | |
| Test Cycle- how many cycle | |
| Start and End date for cycles | |
| Roles and Responsibilities => | Team members are listed |
| Who is to do what | |
| module owners are listed and their contact info | |
| Deliverables => | What documents(test artifacts) are going to produce at what time frames? |
| What can be expected from each document? | |
| Environment => | What kind of environment requirements exist? |
| Who is going to be in charge? | |
| What to do in case of problems? | |
| Tools => | For Example, JIRA for bug tracking |
| Defect Management => | Who are we going to report the defects to? |
| How are we going to report? | |
| What is expected- do we provide screenshot? | |
| Risks and Risk Management => | Risks are listed |
| Risks are analyzed- likelihood and impact is documented | |
| Risk mitigation plans are drawn | |
| Exit criteria => | When to stop testing? |
A Test plan to test features of a new mobile phone (Blackbox test) that needs to be implemented.
if(product owner long press the power button)
{
open the company logo at centre; //As a Product owner,when long pressed the power button of the phone shall switch on with a company logo at the center of the screen.
}
else if(customer press the power button)
{
open the apps in grid; // As a Customer,when the power button is pressed my phone is switched ON and all my icons of the APPS shall be present in the grid
}
else if(product owner power on the phone)
{
shows call the phone icon on first position at bottom;// As a Product owner,when the phone is powered ON ,I shall see the "call the phone" icon as the first icon at the bottom bar of my screen.
}
else if(product owner power on the phone)
{
shows Dictionary icon on second position at bottom; //As a Product owner,when the phone is powered ON, I shall see the "Dictionary" icon as the second icon at the bottom bar of my screen.
}
else if(product owner click on call the phone icon)
{
contacts appears in chronological order;//As a Product owner,when I Clicked my "call the phone" icon ,all the contacts shall be visible based on chronological order.
}
else if(product owner click on Dictionary icon)
{
search bar appears at centre;//As a Product owner,when I Clicked my "Dictionary icon ,a search bar shall appear at the middle of the screen to let me search the meanings of the words I desire.
}
else if(product owner long press power on button)
{
displays Good-Bye and gets switched off;//As a Product owner,when I long pressed my "power on" button ,my phone shall be switched off saying "Good-Bye” Message.
}
else if(product owners phone font)
{
always in calibri with size of 12;//As a product owner ,my font in the mobile shall always be ''calibri (Body)" and shall be of size 12.
}
else if(customer requirement touch responsive)
{
reflects on touch;//As a Customer,I need my UI to be touch responsive.
}
else ( customer requirement no hard buttons)
{
touch screen sensitive;//As a customer ,my mobile phone should have no hard buttons.
}