Project 1 - V&V SW Analysis - I
A]
Test Plan:
A Test Plan refers to a detailed document that catalogs the test strategy, objectives, schedule, estimations, deadlines, and the resources required for completing that particular project.
Test design techniuqes:
1.Equivalence class and boundary check-Boundary value analysis is testing at the boundaries between partitions. Equivalent Class allows you to divide set of test condition into a partition which should be considered the same.
2.Classification Tree Method(CTM)-This technique draw a tree and then find the test case.This technique does not repeats the test cases.
3.Elementary Comparison Test(ECT)-It is a thorough technique for the detailed testing of the functionality.
4.Control Flow Table(CFT)-This technique designs a unique path and no path is left.The first and last point should be constant for every tester.
5.State Transition Technique(STT)-This technique decides legal and illegal cases.This is similar to Finite State Machine.
6.Error Guessing(EG)-Error guessing is a type of testing method in which prior experience in testing is used to uncover the defects in software.For this technique experienced test engineers are required.
Test case attributes:
1.Test case ID:This field uniquely identifies a test case.The test case should include its number, a description, the test data, expected result, actual result and status.
2.Verification method-Verification is all about testing whether your software product satisfies the conditions you specified in the initial stages of development.
3.Testing status:Test case status is an automatically calculated status that indicates the state of the last edited test run associated with that test case.
4.Responsible team:Whole team
5.Maturity:This indicates status of the requirements and shows weather Ready, in phase or reviewed
6.Module name
7.Pre conditions: preconditions specify the setup needed for a test case to be executed successfully for the software test.
8.Test procedure:This includes test input actions, sequential steps etc.
9.Expected result:Expected Result is an ideal result that the tester should get after the test case is performed.
10.Actual result: A result, which a tester gets after performing the test ,given by the tool.
11.Test method: ECT,CTM,STT,EQ,CFT.
12.Test responsible:One person
13.Test designer: The Test Designer role is responsible for defining the test approach and ensuring it's successful implementation.It is similar to Architects(frame the protocol).
14.SIL:SIL stands for Safety Integrity Level. SIL is a measure of safety system performance, in terms of probability of failure on demand.
15.Automation:Test automation is the practice of automatically reviewing and validating a software product.
16.Release: From when onwards the test case is applicable.
17.Valid until release: Valid till when.
18.Customer demo:The test case which should be a part of the customer demo has to be decided.
Testing types:
1.Unit test:Unit tests are very low level and close to the source of an application. They consist in testing individual methods and functions of the classes, components, or modules used by your software.
2.Integration test:Integration tests verify that different modules or services used by your application work well together.
US-1: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.
if(long pressed the power button of the phone)
{
company logo at the center of the screen;
}
else
{
press the button properly;
}
US- 2: 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.
if(power button is pressed)
{
Mobile is switched ON and shows all the icons of the APPS in the grid;
}
else
{
show blank screen;
}
US- 3: 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.
if(power button is ON)
{
show "call the phone" icon as the first icon at the bottom bar of the screen;
}
else
{
show "date and time";
}
US- 4: 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.
if(power button is ON)
{
show "Dictionary" icon as the second icon at the bottom bar of the screen;
}
else
{
show "nothing to show";
}
US-5: As a product owner,when I Clicked my "call the phone" icon,all the contact shall be visible based on chronological order.
if(clicked on "call the phone" icon)
{
all the contacts visible based on chronological order;
}
else
{
all the contacts visible in any order;
}
US- 6: 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.
if(clicked on "Dictionary" icon)
{
a search bar appears at the middle of the screen;
}
else
{
nothing appears;
}
US- 7: As a Product owner,when I long pressed my "power on" button ,my phone shall be switched off saying "Good-Bye” Message.
if(long pressed "power on" button)
{
phone gets switched off saying "Good-Bye”;
}
else
{
nothing appears;
}
US-8: As a product owner ,my font in the mobile shall always be ''calibri (Body)" and shall be of size 12.
if(mobile font)
{
always in calibri with size of 12;
}
else
{
show "nothing to show";
}
US-9:As a Customer,I need my UI to be touch responsive.
if(customer requirement is touch responsive)
{
reflects on touch;
}
else
{
nothing happens;
}
US-10: As a customer ,my mobile phone should have no hard buttons.
if(phone should have no hard buttons)
{
touch screen sensitive;
}
else
{
no response;
}