UNITED INSTITUTE OF TECHNOLOGY (284)

NAINI, PRAYAGRAJ
(Affiliated to Dr. A.P.J Abdul Kalam Technical University, Lucknow)

SOFTWARE TESTING LAB

(KCS-751A)
for

7th SEMESTER

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING&

INFORMATION TECHNOLOY

NAME:
…………………………………………………………

ROLL NO:
…………………………………………………………

BRANCH/SEM/SEC:
…………………………………………………………
 INDEX

Sr.
No.
List of Programs Page No. Date Remarks

Design Test Cases for Purchase Order

1.
Management based on System Specification.

Design Test Cases for Inventory Management

2.
System based on System Specification.

Design Test Cases for Calculator to verify its

3.
Functionality.

Test Various Functionality of Railway

4.
Reservation System.

Validate Login Procedure for E-Commerce

5.
Application.
 Study and Evaluation Scheme of Software Testing Lab
(KCS-751A)

Total No. of Periods: 2 per week

Sessional Evaluation
Internal Evaluation (I) External Evaluation (E)
Sr. No. Criteria Marks Sr. No. Criteria Marks
Written and
1.
1. Teacher’s 25 Machine Test 25
25
Assessment Marks 2. Marks
Viva

TOTAL MARKS(I+E) 50 Marks

CREDIT 1
 Design Test Cases for Purchase Order
Management based on System Specification

What are software testing objectives and purpose?

 Finding defects which may get created by the programmer while developing
the software.
 Gaining confidence in and providing information about the level of quality.
 To prevent defects.
 To make sure that the end result meets the business and user requirements.
 To ensure that it satisfies the BRS that is Business Requirement
Specification and SRS that is System Requirement Specifications.
 To gain the confidence of the customers by providing them a quality
product.

What is test cases and its parameters?

 The test case is defined as a group of conditions under which a tester
determines whether a software application is working as per the customer's
requirements or not. Test case designing includes preconditions, case name,
input conditions, and expected result. A test case is a first level action and
derived from test scenarios.
 Test case parameters are:
1. Test Case IDs
2. Test Objectives
3. Pre Condition
4. Url Optional
5. Test Step 5
6. Test Data
7. Expected Result
8. Actual Result
9. Pass or Fail
Following are the Test case of Purchase Order Management based on
System Specification :-

Test Test Steps Inputs Expected Actual Status

Case Id Case Results results
name

TC-01 Item name Enter item “Prd 1” Product Accepting Passs

name in name
the should be
alphabet accepted

TC-02 Quantity Enter item 1000 Product Accepting Pass

Available name in quantity
number should be
accepted
TC-03 Item Cot Enter item “Prd -1” Product Accepting Pass
name in name
alphabets should be
accepted

TC-04 Submit Click on It should Its is Pass

submit go to next going to
button page next page

TC-05 Cancel Click on It should Its is Pass

cancil remain on remaining
button the page on the
same page
Design Test Cases for Inventory Management System
based on System Specification.

What are the major system specifications of inventory management

system?
1. Indent/Purchase request: Item UOIT (unit of measurement) user item
quantity re order quantity.
2. Request for quatation: Vendor quantation constraints item quantity.
3. Quantation Comparison: No. of quantation comparison criteria min,max
selection.
4. Purchase Order: Reference Quantation item list & Quantation item list &
Quantities terms and conditions.
5. Unloading: Unloading slip unloading data entry form.
6. Inspection: acceptance ,rejection constraints ,inspection report.
7. Allocation: Warehouse no. pack no.
8. Issue: User code Issue authority issue quantity
9. Returns : Returns reason stock adjustments.

What are the function of Inventory Systems?

1. Simplified inventory management
2. Increased productivity and efficiency
3. Increased Profitabilty
4. Avoid stock outs and excess stock
5. Quality management
6. Balancing supply and demand
7. Forecasting and planning
8. Inventory reports
9. All in one solution
Following are the Test case of Inventory Management System based on
System Specification:-

Test Test Pre- Steps I/P data Expected Actual Status

Case Case requisites Results Results
ID Name

TC- Check 1.click on No No Number Number Pass

01 the no. field should be is the
mobile 2.Enter entered collection
number number as the of integer
integer
from a
tag

TC- Check Available Fill the Text/Number Email id It is Pass

02 the in the email id should be collection
email option and clear of no.
password and
alphabets
 Design Test Cases for Calculator to verify its
Functionality.

1)Perform Different type of additions

TC-01: Add two positive number

TC-02: Add 1st +ve and 2nd –ve no.

TC-03: Add 1st –ve and 2nd +ve no.

TC-04: Add both –ve no.

TC-05: Add +ve and zero

TC-06: Add two zeros

TC-07 Add –ve and zero

TC-08: Add +ve and -ve

TC-09: Add –ve and +ve

TC-10: Add +ve and +ve

TC-11: Add -ve and -ve

3)Perform additon of two positive and two negative.

Positive no.

1. Enter 1st no
2. Enter 2nd no
3. Enter or pass additon(+button)
4. Check the final result is ok or not.
Negative no.

1. Check only numeric digits could be accepted

2. Check only 2 number are entered or not
3. Check the addition is working properly
4. Check result is ok or not.
Following are the Test case for calculator to verify its functionality:-
Test Test Pre- Steps I/P Expected Actual Status
Case Case requisites data Results Results
ID Name
TC-01 To add Calculator1.key in a 135 235 235 Pass
two is validating +
to
integer switched 100
999999
and on to
display 999999
result 2. key in
operator
+
TC-02 To Calculator 1.key in a 500 300 300 Pass
subtract is validating -
two switched to 200
999999
integer on to
and 999999
display 2. key in
result operator
-
TC-03 To Calculator 1.key in a 10 200 200 Pass
mulitply is validating *
two switched to 20
999999
integer on to
and 999999
display 2. key in
result operator
*
TC-04 To Calculator 1.key in a 60 30 30 Pass
divide is validating /
two switched to 2
999999
integer on to
and 999999
display 2. key in
result operator
/
 Test Various Functionality of Railway Reservation
System.

Following are the Test case for functionality of Railway Reservation

System:-
Test Case Test Case Input data Expected Actual Status
ID Name Results Results

TC-01 Login failed Any valid Its should Login name Pass
login name accept login accepted
name

TC-02 Password Invalid Should not Message Pass

field password accept displayed
wrong invalid
password login or
pass

TC-03 Password Valid Valid pass Sucessfully Pass

field password should be login
accepted

TC-04 Date of Date format Its should Message pass

journey not before accept accept
current date
 Validate Login Procedure for E-Commerce
Application.

Following are the Test case for Validate Login Procedure for E-
Commerce Application:-

Test Case Test Case Input data Expected Actual Status

ID Name Results Results

TC-01 Register Any valid Its should Login id Pass

new user login id accept login pass
and name and accepted
password password

TC-02 Login id Enter valid Should Sucessfully Pass

and id with its accept id login into
password password and pass the system
check

TC-03 Login id or Wrong id Should not Does not Pass

Password or password accept login
failed wrong id or
password

TC-04 OTP Otp If match otp Login Pass

generation received on then login sucessfully
number sucessfully
 ST LAB

Program 1: Triangle Problem (Testing Technique: Boundary Value Analysis).

Design and develop a program in a language of your choice to solve the triangle problem defined as
follows: Accept three integers which are supposed to be the three sides of a triangle and determine if the
three values represent an equilateral triangle, isosbva1eles triangle, scalene triangle, or they do not form a
triangle at all. Assume that the upper limit for the size of any side is 10. Derive test cases for your program
based on boundary-value analysis, execute the test cases and discuss the results.

#include<stdio.h>
#include<conio.h>
int main( )
{
int a,b,c,c1,c2,c3;
do
{
printf("enter the sides of triangle\n");
scanf("%d%d%d",&a,&b,&c);
c1=((a>=1) && (a<=10));
c2=((b>=1) && (b<=10));
c3=((c>=1) && (c<=10));
if(!c1)
printf("value of a is out of range");
if(!c2)
printf("value of b is out of range");
if(!c3)
printf("value of c is out of range");
}while(!c1 || !c2 || !c3);
if((a+b)>c && (b+c)>a && (c+a)>b)
{
if(a==b && b==c)
printf("Triangle is equilateral\n");
else if(a!=b && b!=c && c!=a)
printf("Triangle is scalene\n");
else
printf("Triangle is isosceles\n");
}
else
printf("Triangle cannot be formed \n");
getch( );
return 0;

BY: Yasharth Mishra (2102840100190) CS-A 4TH Year

Boundary Value Analysis :Boundary value analysis focuses on the boundary of the input and output space
to identify test cases because errors tend to occur near the extreme values of an input variable. The basic
idea is to use input variables at their minimum, just above minimum, nominal, just below their maximum
and maximum.
Considering Triangle program, we have three variables a, b and c. Each variables value ranges from 1 to 10.

Variable Min Min+ Nom Max- Max

a 1 2 5 9 10
b 1 2 5 9 10
c 1 2 5 9 10

Boundary Value Analysis = 4n+1 test cases, where n is number of variables

In Triangle program for BVA, we start by taking nominal values for a and b variables then cross product it
with values min, min-, nom, max- and max values of variable c. similarly keeping nominal values for
variables a and c, we cross product it with min, min-, nom, max-, max values of variable b. Again keeping
variable b and c as nominal combine with 5 values of a. By this we get 15 test cases in which a test case
with all nominal values for a, b and c is repeated thrice, so we discard 2 duplicate such cases and finally we
get 15-2=13 test cases which is equal to BVA i.e., 4(3)+1=13.

Test cases using Boundary value analysis for Triangle Program

Test Description Inputs (A, B, Output Comments
Case C)
BVA 1 Enter the values of a(nom), b(nom), and 5, 5, 1 Isosceles Valid
c(min)
BVA 2 Enter the values of a(nom), b(nom), and 5, 5, 2 Isosceles Valid
c(min+)
BVA 3 Enter the values of a(nom), b(nom), and 5, 5, 5 Equilateral Valid
c(nom)
BVA 4 Enter the values of a(nom), b(nom), and 5, 5, 9 Isosceles Valid
c(max-)
BVA 5 Enter the values of a(nom), b(nom), and 5, 5, 10 Triangle cannot be Valid
c(max) formed
BVA 6 Enter the values of a(nom), b(min), and 5, 1, 5 Isosceles Valid
c(nom)
BVA 7 Enter the values of a(nom), b(min+), and 5, 2, 5 Isosceles Valid
c(nom)
BVA 8 Enter the values of a(nom), b(max-), and 5, 9, 5 Isosceles Valid
c(nom)
BVA 9 Enter the values of a(nom), b(max), and 5, 10, 5 Triangle cannot be Valid
c(nom) formed
BVA 10 Enter the values of a(min), b(nom), and 1, 5, 5 Isosceles Valid
c(nom)
BVA 11 Enter the values of a(min+), b(nom), and 2, 5, 5 Isosceles Valid
c(nom)
BVA 12 Enter the values of a(max-), b(nom), and 9, 5, 5 Isosceles Valid
c(nom)
BVA 13 Enter the values of a(max), b(nom), and 10, 5, 5 Triangle cannot be Valid
c(nom) formed

BY: Yasharth Mishra (2102840100190) CS-A 4TH Year

 ST LAB

Program 2: Commission Problem (Testing Technique: Boundary Value Analysis)

Design, develop, code and run the program in any suitable language to solve the commission problem.
Analyse it from the perspective of boundary value testing, derive different test cases, execute these test cases
and discuss the test results.

#include<stdio.h>
#include<conio.h>
int main()
{
int locks, stocks, barrels, t_sales, flag = 0;
float commission;
printf("Enter the total number of locks");
scanf("%d",&locks);
if ((locks <= 0) || (locks > 70))
{
flag = 1;
}
printf("Enter the total number of stocks");
scanf("%d",&stocks);
if ((stocks <= 0) || (stocks > 80))
{
flag = 1;
}
printf("Enter the total number of barrelss");
scanf("%d",&barrels);
if ((barrels <= 0) || (barrels > 90))
{
flag = 1;
}
if (flag == 1)
{
printf("invalid input");
getch();
}
t_sales = (locks * 45) + (stocks * 30) + (barrels * 25);
if (t_sales <= 1000)
{
commission = 0.10 * t_sales;
}
else if (t_sales < 1800)
{
commission = 0.10 * 1000;
commission = commission + (0.15 * (t_sales - 1000));
}

BY: Yasharth Mishra (2102840100190) CS-A 4TH Year

 else
{
commission = 0.10 * 1000;
commission = commission + (0.15 * 800);
commission = commission + (0.20 * (t_sales - 1800));
}
printf("The total sales is %d \n The commission is %0.2f",t_sales,commission);
getch();
return 0;
}

Considering Commission program, we have three input variables lock, stock and barrels. Range of value for
locks= 1-70, stocks= 1-80 and barrels= 1-90

Variable Min Min+ Nom Max- Max

Locks 1 2 35 69 70
Stocks 1 2 40 79 80
Barrels 1 2 45 89 90

Considering output variable sales we have 3 slots for calculating commission. i.e., if sales are below 1000,
com is 10%, if sales are 1001 to 1800 then com is 15% and if sales are greater than 1801, com is 20%.

Min (Locks, Min+ (Locks, Nom (Locks, Max- (Locks, Max (Locks,
Sales
Stocks, Barrels) Stocks, Barrels) Stocks, Barrels) Stocks, Barrels) Stocks, Barrels)
2, 1, 1 9, 10, 10
1-1000 1, 1, 1 1, 2, 1 5, 5, 5 10, 9, 10 10, 10, 10
1, 1, 2 10, 10, 9
11, 10, 10 10, 11, 10 17, 18, 18
1001-
10, 11, 10 10, 12, 10 14, 14, 14 18, 17, 18 18, 18, 18
1800
10, 10, 11 10, 10, 12 18, 18, 17
19, 18, 18 20, 18, 18 69, 80, 90
1801-
18, 19, 18 18, 20, 18 48, 48, 48 70, 79, 90 70, 80, 90
above
18, 18, 19 18, 18, 20 70, 80, 89

BY: Yasharth Mishra (2102840100190) CS-A 4TH Year

Test cases for commission program using INPUT Boundary value analysis

Inputs Output
Test
Description (Locks, Stocks, (Sales, Comments
Case Barrels) Com)

Enter the values for locks (nom), stocks

BVA1 35, 40, 1 2800, 420 Valid
(nom), and barrels (min)

Enter the values for locks (nom), stocks

BVA2 35, 40, 2 2825, 425 Valid
(nom), and barrels (min+)

Enter the values for locks (nom), stocks

BVA3 35, 40, 45 3900, 640 Valid
(nom), and barrels (nom)

Enter the values for locks (nom), stocks

BVA4 35, 40, 89 5000, 860 Valid
(nom), and barrels (max-)

Enter the values for locks (nom), stocks

BVA5 35, 40, 90 5025, 865 Valid
(nom), and barrels (max)

Enter the values for locks (nom), stocks

BVA6 35, 1, 45 2730, 406 Valid
(min), and barrels (nom)

Enter the values for locks (nom), stocks

BVA7 35, 2, 45 2760, 412 Valid
(min+), and barrels (nom)

Enter the values for locks (nom), stocks

BVA8 35, 79, 45 5070, 874 Valid
(max-), and barrels (nom)

Enter the values for locks (nom), stocks

BVA9 35, 80, 45 5100, 880 Valid
(max), and barrels (nom)

Enter the values for locks (min), stocks

BVA10 1, 40, 45 2370, 334 Valid
(nom), and barrels (nom)

Enter the values for locks (min+), stocks

BVA11 2, 40, 45 2415, 343 Valid
(nom), and barrels (nom)

Enter the values for locks (max-), stocks

BVA12 69, 40, 45 5430, 946 Valid
(nom), and barrels (nom)

Enter the values for locks (max), stocks

BVA13 70, 40, 45 5475, 955 Valid
(nom), and barrels (nom)

BY: Yasharth Mishra (2102840100190) CS-A 4TH Year

Test cases for commission program using OUTPUT Boundary value analysis

Test
Description Inputs Output Comments
Cases
Enter the values for locks(min), stocks(min), and Locks: 1, Stocks: Sales: 100,
BVA1 Valid
barrels(min) for the range 100 to 1000 1, Barrels: 1 Commission: 10
Enter the values for locks(min+), stocks(min), and Locks: 2, Stocks: Sales: 145,
BVA2 Valid
barrels(min) for the range 100 to 1000 1, Barrels: 1 Commission: 14.5
Enter the values for locks(min), stocks(min+), and Locks: 1, Stocks: Sales: 130,
BVA3 Valid
barrels(min) for the range 100 to 1000 2, Barrels: 1 Commission: 13
Enter the values for locks(min), stocks(min), and Locks: 1, Stocks: Sales: 125,
BVA4 Valid
barrels(min+) for the range 100 to 1000 1, Barrels: 2 Commission: 12.5
Enter the values for locks(nom), stocks(nom), and Locks: 5, Stocks: Sales: 500,
BVA5 Valid
barrels(nom) for the range 100 to 1000 5, Barrels: 5 Commission: 50
Enter the values for locks(max-), stocks(max), and Locks: 9, Stocks: Sales: 955,
BVA6 Valid
barrels(max) for the range 100 to 1000 10, Barrels: 10 Commission: 95.5
Enter the values for locks(max), stocks(max-), and Locks: 10, Stocks: Sales: 970,
BVA7 Valid
barrels(max) for the range 100 to 1000 9, Barrels: 10 Commission: 97.0
Enter the values for locks(max), stocks(max), and Locks: 10, Stocks: Sales: 975,
BVA8 Valid
barrels(max-) for the range 100 to 1000 10, Barrels: 9 Commission: 97.5
Enter the values for locks(max), stocks(max), and Locks: 10, Stocks: Sales: 1000,
BVA9 Valid
barrels(max) for the range 100 to 1000 10, Barrels: 10 Commission: 100
Enter the values for locks(min), stocks(min), Locks: 11, Stocks: Sales: 1045,
BVA10 Valid
and barrels(min) for the range 1000 to 1800 10, Barrels: 10 Commission: 106.75
Enter the values for locks(min), stocks(min+), Locks: 10, Stocks: Sales: 1030,
BVA11 Valid
and barrels(min) for the range 1000 to 1800 11, Barrels: 10 Commission: 104.5
Enter the values for locks(min), stocks(min), Locks: 10, Stocks: Sales: 1025,
BVA12 Valid
and barrels(min+) for the range 1000 to 1800 10, Barrels: 11 Commission: 103.75
Enter the values for locks(min+), stocks(min), Locks: 12, Stocks: Sales: 1090,
BVA13 Valid
and barrels(min) for the range 1000 to 1800 10, Barrels: 10 Commission: 113.5
Enter the values for locks(min), stocks(min+), Locks: 10, Stocks: Sales: 1060,
BVA14 Valid
and barrels(min) for the range 1000 to 1800 12, Barrels: 10 Commission: 109
Enter the values for locks(min), stocks(min), and Locks: 10, Stocks: Sales: 1050,
BVA15 Valid
barrels(min+) for the range 1000 to 1800 10, Barrels: 12 Commission: 107.5
Enter the values for locks(nom), stocks(nom), Locks: 14, Stocks: Sales: 1400,
BVA16 Valid
and barrels(nom) for the range 1000 to 1800 14, Barrels: 14 Commission: 160
Enter the values for locks(max-), stocks(max), Locks: 17, Stocks: Sales: 1755,
BVA17 Valid
and barrels(max) for the range 1000 to 1800 18, Barrels: 18 Commission: 213.25
Enter the values for locks(max), stocks(max-), Locks: 18, Stocks: Sales: 1770,
BVA18 Valid
and barrels(max) for the range 1000 to 1800 17, Barrels: 18 Commission: 215.5
Enter the values for locks(max), stocks(max), Locks: 18, Stocks: Sales: 1775,
BVA19 Valid
and barrels(max-) for the range 1000 to 1800 18, Barrels: 17 Commission: 216.25

BY: Yasharth Mishra (2102840100190) CS-A 4TH Year

 Enter the values for locks(max), stocks(max), Locks: 18, Stocks: Sales: 1800,
BVA20 Valid
and barrels(max) for the range 1000 to 1800 18, Barrels: 18 Commission: 220
Enter the values for locks(min), stocks(min), Locks: 19, Stocks: Sales: 1845,
BVA21 Valid
and barrels(min) for the range > 1800 18, Barrels: 18 Commission: 229
Enter the values for locks(min), stocks(min), Locks: 18, Stocks: Sales: 1830,
BVA22 Valid
and barrels(min) for the range > 1800 19, Barrels: 18 Commission: 226
Enter the values for locks(min), stocks(min), Locks: 18, Stocks: Sales: 1825,
BVA23 Valid
and barrels(min) for the range > 1800 18, Barrels: 19 Commission: 225
Enter the values for locks(min+), stocks(min), Locks: 20, Stocks: Sales: 1890,
BVA24 Valid
and barrels(min) for the range > 1800 18, Barrels: 18 Commission: 238
Enter the values for locks(min), stocks(min+), Locks: 18, Stocks: Sales: 1860,
BVA25 Valid
and barrels(min) for the range > 1800 20, Barrels: 18 Commission: 232
Enter the values for locks(min), stocks(min), Locks: 18, Stocks: Sales: 1850,
BVA26 Valid
and barrels(min+) for the range > 1800 18, Barrels: 20 Commission: 230
Enter the values for locks(nom), stocks(nom), Locks: 48, Stocks: Sales: 4800,
BVA27 Valid
and barrels(nom) for the range > 1800 48, Barrels: 48 Commission: 820
Enter the values for locks(max-), stocks(max), Locks: 69, Stocks: Sales: 7755,
BVA28 Valid
and barrels(max) for the range > 1800 80, Barrels: 90 Commission: 1411
Enter the values for locks(max), stocks(max-), Locks: 70, Stocks: Sales: 7770,
BVA29 Valid
and barrels(max) for the range > 1800 79, Barrels: 90 Commission: 1414
Enter the values for locks(max), stocks(max), Locks: 70, Stocks: Sales: 7775,
BVA30 Valid
and barrels(max-) for the range > 1800 80, Barrels: 89 Commission: 1415
Enter the values for locks(max), stocks(max), Locks: 70, Stocks: Sales: 7800,
BVA31 Valid
and barrels(max) for the range > 1800 80, Barrels: 90 Commission: 1420

BY: Yasharth Mishra (2102840100190) CS-A 4TH Year

 ST LAB

Program 3: Next date program (Testing Technique: Boundary Value Analysis)

Design, develop, code and run the program in any suitable language to implement the
NextDate function. Analyze it from the perspective of boundary value testing, derive
different test cases, execute these test cases and discuss the test results.

#include<stdio.h>

int check(int day, int month)

{
if((month == 4 || month == 6 || month == 9 || month == 11) && day == 31)
return 1;
else
return 0;
}

int isleap(int year)

{
if((year % 4 == 0 && year % 100 != 0) || year % 400 == 0)
return 1;
else
return 0;
}

int main()
{
int day, month, year, tomm_day, tomm_month, tomm_year;
char flag;
do
{
flag = 'y';
printf("\nenter today's date in the form of dd mm yyyy\n");
scanf("%d%d%d", &day, &month, &year);
tomm_month = month;
tomm_year = year;

if(day < 1 || day > 31)

{
printf("value of day, not in the range 1...31\n");
flag = 'n';
}
if(month < 1 || month > 12)
{
printf("value of month, not in the range 1...12\n");
flag = 'n';
}
else if(check(day, month))

BY: Yasharth Mishra (2102840100190) CS-A 4TH Year

 {
printf("value of day, not in the range day <= 30\n");
flag = 'n';
}
if(year <= 1812 || year > 2015)
{
printf("value of year, not in the range 1812...2015\n");
flag = 'n';
}
if(month == 2)
{
if(isleap(year) && day > 29)
{
printf("invalid date input for leap year\n");
flag = 'n';
}
else if(!(isleap(year)) && day > 28)
{
printf("invalid date input for not a leap year\n");
flag = 'n';
}
}
} while(flag == 'n');

switch (month)
{
case 1:
case 3:
case 5:
case 7:
case 8:
case 10:
if(day < 31)
tomm_day = day + 1;
else
{
tomm_day = 1;
tomm_month = month + 1;
}
break;

case 4:
case 6:
case 9:
case 11:
if(day < 30)
tomm_day = day + 1;
else
{
tomm_day = 1;
tomm_month = month + 1;
}
BY: Yasharth Mishra (2102840100190) CS-A 4TH Year
 break;

case 12:
if(day < 31)
tomm_day = day + 1;
else
{
tomm_day = 1;
tomm_month = 1;
if(year == 2015)
{
printf("the next day is out of boundary value of year\n");
tomm_year = year + 1;
}
else
tomm_year = year + 1;
}
break;

case 2:
if(day < 28)
tomm_day = day + 1;
else if(isleap(year) && day == 28)
tomm_day = day + 1;
else if(day == 28 || day == 29)
{
tomm_day = 1;
tomm_month = 3;
}
break;
}
printf("next day is: %d %d %d", tomm_day, tomm_month, tomm_year);
return 0;
}

Considering Date program, we have three variables day, month and year.

Variable Min Min+ Nom Max- Max

day 1 2 15 30 31

month 1 2 6 11 12

year 1812 1813 1914 2014 2015

BY: Yasharth Mishra (2102840100190) CS-A 4TH Year

 Test cases for Date program using Boundary Value Analysis

Test Description Inputs (DD MM Output Comments

Case YY)
BVA1 Enter the values for day(nom), month(nom), 15 6 1812 16/6/1812 Valid
and year(min)
BVA2 Enter the values for day(nom), month(nom), 15 6 1813 16/6/1813 Valid
and year(min+)
BVA3 Enter the values for day(nom), month(min), 15 6 1914 16/6/1914 Valid
and year(nom)
BVA4 Enter the values for day(nom), month(nom), 15 6 2014 16/6/2014 Valid
and year(max-)
BVA5 Enter the values for day(nom), month(nom), 15 6 2015 16/6/2015 Valid
and year(max)
BVA6 Enter the values for day(nom), month(min), 15 1 1914 16/1/1914 Valid
and year(nom)
BVA7 Enter the values for day(nom), month(min+), 15 2 1914 16/2/1914 Valid
and year(nom)
BVA8 Enter the values for day(nom), month(max-), 15 11 1914 16/11/1914 Valid
and year(nom)
BVA9 Enter the values for day(nom), month(max), 15 12 1914 16/12/1914 Valid
and year(nom)
BVA10 Enter the values for day(min), month(nom), 1 6 1914 2/6/1914 Valid
and year(nom)
BVA11 Enter the values for day(min+), month(nom), 2 6 1914 3/6/1914 Valid
and year(nom)
BVA12 Enter the values for day(max-), month(nom), 30 6 1914 1/7/1914 Valid
and year(nom)
BVA13 Enter the values for day(max), month(nom), 31 6 1914 Day out of Valid
and year(nom) range

BY: Yasharth Mishra (2102840100190) CS-A 4TH Year

 Design Test Cases for Purchase Order Management based on System Specification
What are software testing objectives and purpose?

• Finding defects which may get created by the programmer while developingthe software.
• Gaining confidence in and providing information about the level of quality.

• To prevent defects.

• To make sure that the end result meets the business and user requirements.

• To ensure that it satisfies the BRS that is Business Requirement Specification and
SRS that is System Requirement Specifications.

• To gain the confidence of the customers by providing them a qualityproduct.

What is test cases and its parameters?

• The test case is defined as a group of conditions under which a tester determines whether a
software application is working as per the customer's requirements or not. Test case designing
includes preconditions, case name,input conditions, and expected result. A test case is a first
level action and derived from test scenarios.

• Test case parameters are:

1. Test Case IDs

2. Test Objectives
3. Pre Condition

4. Url Optional

5. Test Step 5
6. Test Data

7. Expected Result

8. Actual Result

9. Pass or Fail
Following are the Test case of Purchase Order Management based onSystem Specification :-
Test Test Steps Inputs Expected Actual Status
Case Id Case Results results
name

TC-01 Item name Enter item “Prd 1” Product Accepting Passs

name in the name
alphabet should be
accepted

TC-02 Quantity Enter item 1000 Product Accepting Pass

Available name in quantity
number should be
accepted

TC-03 Item Cot Enter item “Prd -1” Product Accepting Pass
name in name
alphabets should be
accepted

TC-04 Submit Click on It should go Its is going Pass

submit to nextpage to next page
button

TC-05 Cancel Click on It should Its is Pass

cancil remain on remainingon
button the page the same
page
Design Test Cases for Inventory Management Systembased on System Specification.
What are the major system specifications of inventory managementsystem?

1. Indent/Purchase request: Item UOIT (unit of measurement) user itemquantity re order

quantity.

2. Request for quatation: Vendor quantation constraints item quantity.

3. Quantation Comparison: No. of quantation comparison criteria min,maxselection.

4. Purchase Order: Reference Quantation item list & Quantation item list &Quantities terms
and conditions.

5. Unloading: Unloading slip unloading data entry form.

6. Inspection: acceptance ,rejection constraints ,inspection report.
7. Allocation: Warehouse no. pack no.
8. Issue: User code Issue authority issue quantity
9. Returns : Returns reason stock adjustments.
What are the function of Inventory Systems?
1. Simplified inventory management
2. Increased productivity and efficiency
3. Increased Profitabilty
4. Avoid stock outs and excess stock
5. Quality management
6. Balancing supply and demand
7. Forecasting and planning
8. Inventory reports
9. All in one solution
 Following are the Test case of Inventory Management System based onSystem Specification:-
Test Case Test Pre- Steps I/P data Expected Actual Status
ID Case requisites Results Results
Name
TC-01 Check 1.click on No No Number Number is Pass
the no. field should be the
mobile 2.Enter entered as collectionof
number number the integer integer
from a tag
 Design Test Cases for Calculator to verify its Functionality.
1)Perform Different type of additions
TC-01: Add two positive number TC-

02: Add 1st +ve and 2nd –ve no.TC-03:

Add 1st –ve and 2nd +ve no.TC-04:

Add both –ve no.

TC-05: Add +ve and zero

TC-06: Add two zeros TC-

07 Add –ve and zero TC-

08: Add +ve and -ve TC-

09: Add –ve and +ve TC-

10: Add +ve and +veTC-

11: Add -ve and -ve

3) Perform additon of two positive and two negative.

Positive no.
1. Enter 1st no
2. Enter 2nd no
3. Enter or pass additon(+button)
4. Check the final result is ok or not.
Negative no.

1. Check only numeric digits could be accepted

2. Check only 2 number are entered or not
3. Check the addition is working properly
4. Check result is ok or not.
Following are the Test case for calculator to verify its functionality:-

Test Test Pre- Steps I/P Expected Actual Status

Case Case requisites data Results Results
ID Name
TC-01 To add Calculatoris 1. key in a 135 235 235 Pass
two switched on validating
integer to 999999 +
and 100
to
display
999999
result
2. key in
operator
+

TC-02 To Calculatoris 1. key in a 500 300 300 Pass

subtract switched on validating
two to 999999 -
integer 200
to
and
999999
display
result 2. key in
operator
-

TC-03 To Calculatoris 1. key in a 10 200 200 Pass

mulitply switched on validating
two to 999999 *
integer 20
to
and
999999
display
result 2. key in
operator
*

TC-04 To Calculatoris 1. key in a 60 30 30 Pass

divide switched on validating
two to 999999 /
integer 2
to
and
999999
display
result 2. key in
operator
/
 Test Various Functionality of Railway ReservationSystem.
Following are the Test case for functionality of Railway ReservationSystem:-

Test CaseID Test Case Input data Expected Actual Status

Name Results Results

TC-01 Login failed Any valid Its should Login name Pass
login name accept login accepted
name

TC-02 Password Invalid password Should not Message Pass

field accept wrong displayed
password invalid
login or
pass

TC-03 Password Valid password Valid pass Sucessfully Pass

field should be login
accepted

TC-04 Date of Date formatnot Its should Message pass

journey before current accept accept
date
 Validate Login Procedure for E-CommerceApplication.
Following are the Test case for Validate Login Procedure for E-Commerce Application:-
Test CaseID Test Case Input data Expected Actual Status
Name Results Results

TC-01 Register Any valid Its should Login idpass Pass

new user login id and accept login accepted
password name and
password

TC-02 Login id and Enter validid Should Sucessfully Pass

password with its accept id login into the
check password and pass system

TC-03 Login id or Wrong id or Should not Does not Pass

Password password accept wrong login
failed id orpassword

TC-04 OTP Otp received If match otp Login Pass

onnumber then login sucessfully
generation sucessfully
 Write a programs in C language in demonstration the working of the
following constructs i) do..while ii) while..do iii) if…else iv)switch v) for
Syntax:
Iteration-statement:
do statement while ( expression ) ;
Example:
#include<stdio.h>
#include<conio.h>
#include <stdio.h>
main()
{
int i = 10;
do{
printf("Hello %d\n", i );
i = i -1;
if( i == 6 )
{
break;
}
}while ( i > 0 );
}

ii.) do..while
while(condition)
{
Loop body
Increment or decrement;
}
Example:
#include<stdio.h>
int main()
{
int counter, howmuch;

scanf("%d", &howmuch);
counter = 0;
while ( counter < howmuch)
{
counter++;
printf("%d\n", counter);
}
return 0;
}
iii) if…else
 syntax:
if( condition 1 )
statement1;
else if( condition 2 )
statement2;
else if( condition 3 )
statement3;
else
statement4;
example:
#include<stdio.h> int
main(){
int x,y;
printf("Enter value for x :");
scanf("%d",&x);
printf("Enter value for y :");
scanf("%d",&y);
if ( x > y ){
printf("X is large number - %d\n",x);
}
else{
printf("Y is large number - %d\n",y);
}

return 0;
}

iv) switch

syntax:
swithch(int/char const)
{
Case const 1:stm1;
Break;
Case const 2:stmt2;
Break;
}
}
default: stmt n;
Break;
}
Example:

#include <stdio.h>

int main() {
int color = 1;
printf("Please choose a color(1: red,2: green,3: blue):\n");
scanf("%d", &color);

switch (color)
{
 case 1:
printf("you chose red color\n");
break;
case 2:
printf("you chose green color\n");
break;
case 3:
printf("you chose blue color\n");
break;
default:
printf("you did not choose any color\n");
}
return 0;
}

v) for
Syntax:

for (initialization; condition; increment/decrement)

{
//body of the loop
}

Example:
#include <stdio.h>
int main()
{
int x;
/* The loop goes while x < 10, and x increases by one every loop*/ for ( x = 0; x
< 10; x++ )
{

/* Keep in mind that the loop condition checks the

conditional statement before it loops again. consequently,
when x equals 10 the loop breaks. x is updated before the
condition is checked. */
printf( "%d\n", x );
}
getchar();
}
Viva questions:
1. How to find entered number is EVEN or ODD without using conditional statement (not
using if.. else, while, do... while...., for ... )
2. Write a function to swap any two numbers?
3. How can we find out prime numbers from 1 to 50?
 A program for written in C language for Matrix Multiplication fails‖
introspect the causes for its failure and write down the possible reasons for
its failure
#include<stdio.h>
#include<conio.h>
Void main()
{
int a[10][10], b[10][10], m[10][10], i, j, p, q, r, s, k; clrscr ();
printf(―enter the size of A Matrix‖);
scanf(―%d %d‖, &p, &q);
printf(―Enter the size of B Matrix ‖);
scanf(―%d %d ―, &r, &s);
if(q=r)
{
printf(―Enter the elements of matrix A:\n‖);
for(i=0; i<p; i++)
{
for(j=0; j<q; j++)
{
scanf(―%d‖, &a[i][j]);
}
}
printf(―Enter the elements of matrix b:\n‖); for(i=0;
i<r; i++)
{
for(j=0; j<s; j++)
{
scanf(―%d‖, &b[i][j]);
}
}
for (i=0; i<p; i++)
{
for(j=0; j<s; j++)
{
m[i][j]=0;
for(k=0; k<q; k++)
{
m[i][j] =m[i][j] +a[i][j] * b[k][j];
}
}}
Printf(―matrix multiplication is:\n‖);
for(i=0; i<p; i++)
{
for(j=0; j<s; j++)
{
Printf(―%d\t‖, m[i][j]);
}
 ` Printf(―\n‖);
}
}
else

printf(―matrix multiplication is not possible‖);

getch();
}
FAILURE CASES:
output:
1. Enter the size of a: 2 3
Enter the size of b: 2 3
Matrix multiplication is not possible.
Reason to fail: to do multiplication of matrices the number of columns in matrix ―a[] should be
equal to number of rows in matrix ―b‖.
2. Enter the size of a: p q
Enter the size of b: q s
Matrix multiplication is not possible.
Reason to fail: to do multiplication of matrices the number of columns in matrix ―a‖ should be
equal to number of rows in matrix ―b‖, and rows & columns should be integer values.
3. Enter the size of a: 1.5 2
Enter the size of b: 2 3
Matrix multiplication is not possible.
Reason to fail: to do multiplication of matrices the number of columns in matrix ―a‖ should be
equal to number of rows in matrix ―b‖, and rows & columns should be integer values.
4. Enter the size of a: 350 480 Enter
the size of b: 480 620
Matrix multiplication is not possible.
Reason to fail: size of buffer will be not be sufficient to handle this multiplication.
5. Enter the size of a: -1 -2
Enter the size of b: -2 3
Matrix multiplication is not possible.
Reason to fail: to do multiplication of matrices the number of columns in matrix ―a‖ should be
equal to number of rows in matrix ―b‖, and rows &
columns should be positive integer values.
viva questions:
1. syntax for multiplication
2. syntax for matrix multiplication
3. what the logic for matrix multiplication?
 Take ATM system specifications and report the various bugs
Purpose:
This document describes the software requirements and specification (SRS) for an automated
teller machine (ATM) network. The document is intended for the customer and the developer
(designers, testers, maintainers). The reader is assumed to have basic knowledge of banking accounts
and account services. Knowledge
and understanding of Unified Modeling Language (UML) diagrams is also required.

Scope:
The software supports a computerized banking network called ‗Bank24„. The network enables
customers to complete simple bank account services via automated teller machines (ATMs) that may
be located off premise and that need not be owned and operated by the customer„s bank. The ATM
identifies a customer by a cash card and password. It collects information about a simple account
transaction (e.g., deposit, withdrawal, transfer, bill payment), communicates the transaction information
to the customer„s bank, and dispenses cash to the customer. The banks provide their own software for
their own computers. The
‗Bank24„ software requires appropriate record keeping and security provisions. The software must
handle concurrent accesses to the same account correctly.
Intended Audience:
The intended audience of this SRS consists of:
• Software designers
• Systems engineers
• Software developers
• Software testers
• Customers
The actors of the system are:
1. User
2. ATM Machine
3. Bank
Product Perspective:
An automated teller machine (ATM) is a computerized telecommunications device that provides the
customers of a financial institution with access to financial transactions in a public space without the
need for a human clerk or bank teller. On most modern ATMs, the customer is identified by inserting
a plastic ATM card with a magnetic stripe or a plastic smartcard with a chip, that contains a unique card
number and some security information, such as an expiration date or CVC (CVV). Security is provided
by the customer entering a personal identification number (PIN).
Product functions:
Using an ATM, customers can access their bank accounts in order to make cash withdrawals (or
credit
card cash advances) and check their account balances.
The functions of the system are:
1. Login
2. Get Balance Information
3. Withdraw Cash
4. Transfer Funds

Operating Environments:
The hardware, software and technology used should have following specifications:
• Ability to read the ATM card.
• Ability to count the currency notes.
• Touch screen for convenience.
• Keypad (in case touchpad fails)
• Continuous power supply.
 • Ability to connect to bank„s network.
• Ability to validate user.

Design/implementation constraints:
Login:
Validate Bank Card
• Validate for Card Expiration Date
• Validate that the card's expiration date is later than today's date
• If card is expired, prompt error message "Card is expired" Validate
for Stolen or Lost Card
• Validate that the card is not reported lost or stolen
• If card is lost, prompt error message, "Card has been reported lost"
• If card is stolen, prompt error message, "Card has been reported
stolen"Validate for Disabled Card
• Validate that the card is not disabled
• If card is disabled, prompt error message, "Card has been disabled
as of <expirationdate>"
Validate for Locked Account
• Validate that the account is not locked
• If account is locked, prompt error message "Account is locked" Validate PIN
• Validate that the password is not blank
• If PIN is blank, prompt error message "Please provide PIN"
• Validate that the password entered matches the password on file
• If password does not match, prompt error message "Password is Incorrect"Lock Account
• If number of consecutive unsuccessful logins exceeds three attempts, lockaccount
Maintain Consecutive Unsuccessful Login Counter
Increment Login Counter
For every consecutive Login attempt, increment logic counter by 1.
Reset login counter to 0 after login is successful.
Get Balance Information
Withdraw Cash
Transfer Funds
Assumptions and Dependencies:
• Hardware never fails
• ATM casing is impenetrable
• Limited number of transactions per day (sufficient paper for receipts)
• Limited amount of money withdrawn per day (sufficient money)

External Interface Requirements

User interfaces
The customer user interface should be intuitive, such that 99.9% of all new ATM users are able to
complete their banking transactions without any assistance.
Hardware interfaces
The hardware should have following specifications:
• Ability to read the ATM card
• Ability to count the currency notes
• Touch screen for convenience
• Keypad (in case touchpad fails)
• Continuous power supply
• Ability to connect to bank„s network
• Ability to take input from user
• Ability to validate userSoftware
interfaces
The software interfaces are specific to the target banking software systems. At present, two known
banking systems will participate in the ATM network.
• State Bank
• Indian Overseas Bank
 Safety requirements:
Must be safe kept in physical aspects, say in a cabin
• Must be bolted to floor to prevent any kind of theft
• Must have an emergency phone outside the cabin
• There must be an emergency phone just outside the cabin
• The cabin door must have an ATM card swipe slot
• The cabin door will always be locked, which will open only when user swipes his/her ATM
card in the slot & is validated as genuine
Security requirements:
• Users accessibility is censured in all the ways
• Users are advised to change their PIN on first use
• Users are advised not to tell their PIN to anyone
• The maximum number of attempts to enter PIN will be three
Some of the possible Bugs on ATM machine?
1. 1.Successful insertion of ATM card
2. Unsuccessful operation due to insert card in wrong angle
3. Unsuccessful operation due to invalid account Ex: other bank card or time expired card
4. successful entry of PIN number
5. un successful operation due to enter wrong PIN number 3times
6. successful selection of language
7. successful selection of account type
8. unsuccessful operation due to invalid account type
9. successful selection of withdraw operation
10. successful selection of amount to be withdrawl
11. successful withdraw operation
12. unsuccessful withdraw operation due to wrong denominations
13. unsuccessful withdraw operation due to amount is greater than day limit
14. unsuccessful withdraw operation due to lack of money in ATM
15. unsuccessful withdraw operation due to amount is greater than possible balance
16. unsuccessful withdraw operation due to transactions is greater than day limit
17. unsuccessful withdraw operation due to click cancel after insert card
18. unsuccessful withdraw operation due to click cancel after insert card & pin number
19. unsuccessful withdraw operation due to click cancel after insert card , pin number & language
20. unsuccessful withdraw operation due to click cancel after insert card , pin number , language
&account type
21. unsuccessful withdrawal operation due to click cancel after insert card , pin number ,
language ,account type & withdrawal operation
22. unsuccessful withdrawal operation due to click cancel after insert card , pin number ,
language ,account type ,withdrawal operation &amount to be withdraw
 Write Test cases for banking applications
Banking applications are considered to be one of the most complex applications in today„s software
development and testing industry. What makes Banking application so complex? What approach
should be followed in order to test the complex workflows involved? In this article we will be
highlighting different stages and techniques involved in testing Banking applications. The
characteristics of a Banking application are as follows:
• Multi tier functionality to support thousands of concurrent user sessions
• Large scale Integration , typically a banking application integrates with numerous other
applications such as Bill Pay utility and Trading accounts
• Complex Business workflows
• Real Time and Batch processing
• High rate of Transactions per seconds
• Secure Transactions
• Robust Reporting section to keep track of day to day transactions
• Strong Auditing to troubleshoot customer issues
• Massive storage system
• Disaster Management.
The above listed ten points are the most important characteristics of a Banking application.
Banking applications have multiple tiers involved in performing an operation. For Example, a
banking application may have:
1. Web Server to interact with end users via Browser
2. Middle Tier to validate the input and output for web server
3. Data Base to store data and procedures
4. Transaction Processor which could be a large capacity Mainframe or any other Legacy
system to carry out Trillions of transactions per second.
If we talk about testing banking applications it requires an end to end testing methodology involving
multiple software testing techniques to ensure:
• Total coverage of all banking workflows and Business Requirements
• Functional aspect of the application
• Security aspect of the application
• Data Integrity
• Concurrency
• User Experience
Typical stages involved in testing Banking Applications are shown in below workflow which we
will be discussing individually.
1) Requirement Gathering:
Requirement gathering phase involves documentation of requirements either as Functional
Specifications or Use Cases. Requirements are gathered as per customer needs and documented by
Banking Experts or Business Analyst. To write requirements on more than one subject experts are
involved as banking itself has multiple sub domains and one full fledge banking application will be the
integration of all. For Example: A banking application may have separate modules for Transfers, Credit
Cards, Reports, Loan Accounts, Bill Payments, Trading Etc.
2) Requirement Review:
The deliverable of Requirement Gathering is reviewed by all the stakeholders such as QA Engineers,
Development leads and Peer Business Analysts. They cross check that neither existing business
workflows nor new workflows are violated.
3) Business Scenario Preparations:
In this stage QA Engineers derive Business Scenarios from the requirement documents (Functions Specs
or Use Cases); Business Scenarios are derived in such a way that all Business Requirements arecovered.
Business Scenarios are high level scenarios without any detailed steps, further these Business Scenarios
are reviewed by Business Analyst to ensure all of Business Requirements are met and its easier for BAs
to review high level scenarios than reviewing low level detailed Test Cases.
4) Functional Testing:
In this stage functional testing is performed and the usual software testing activities are performed
such as:
Test Case Preparation:
In this stage Test Cases are derived from Business Scenarios, one Business Scenario leads to several
positive test cases and negative test cases. Generally tools used during this stage are Microsoft Excel,
Test Director or Quality Center.
Test Case Review:
Reviews by peer QA Engineers
Test Case Execution:
Test Case Execution could be either manual or automatic involving tools like QC, QTP or any
other.
5) Database Testing:
Banking Application involves complex transaction which are performed both at UI level and Database
level, Therefore Database testing is as important as functional testing. Database in itself is an entirely
separate layer hence it is carried out by database specialists and it uses techniques like
• Data loading
• Database Migration
• Testing DB Schema and Data types
• Rules Testing
• Testing Stored Procedures and Functions
• Testing Triggers
• Data Integrity
6) Security Testing:
Security Testing is usually the last stage in the testing cycle as completing functional and non functional
are entry criteria to commence Security testing. Security testing is one of the major stagesin the entire
Application testing cycle as this stage ensures that application complies with Federal and Industry
standards. Security testing cycle makes sure the application does not have any web vulnerability which
may expose sensitive data to an intruder or an attacker and complies withstandards like OWASP.
In this stage the major task involves in the whole application scan which is carried out using tools like
IBM Appscan or HP WebInspect (2 Most popular tools).
Once the Scan is complete the Scan Report is published out of which False Positives are filtered out
and rest of the vulnerability are reported to Development team for fixing depending on the Severity.
Other Manual tools for Security Testing used are: Paros Proxy, Http Watch, Burp Suite, Fortify tools
Etc.
Apart from the above stages there might be different stages involved like Integration Testing and
Performance Testing.
In today„s scenario majority of Banking Projects are using: Agile/Scrum, RUP and Continuous
Integration methodologies, and Tools packages like Microsoft„s VSTS and Rational Tools.
As we mentioned RUP above, RUP stands for Rational Unified Process, which is an iterative software
development methodology introduced by IBM which comprises of four phases in which development
and testing activities are carried out.
Four phases are:
i) Inception
ii) Collaboration
iii) Construction and
iv) Transition
RUP widely involves IBM Rational tools.
In this article we discussed how complex a Banking application could be and what are the typical
phases involved in testing the application. Apart from that we also discussed current trends followed
by IT industries including software development methodologies and tools.
Test cases for opening bank account
1. Input parameters checking -
Name
-Date of Birth -
Photo -Address
Proof -Identity
proof
-Introducers (if applicable) -
PAN card
-Initial deposit
-Whether checkbook / ATM card / Online banking facilities are needed or not -Customer
signature
Type of account -
Savings account -Salary
account -Joint account -
Current account -
Secondary account -RD
account
-Account for a company
Test cases
-Checking mandatory input parameters -Checking
optional input parameters -Check whether able to
create account entity.
-Check whether you are able to deposit an amount in the newly created account (and thus updating the
balance)
-Check whether you are able to withdraw an amount in the newly created account (after deposit) (and
thus updating the balance)
-Check whether company name and its pan number and other details are provided in case of salary
account
-Check whether primary account number is provided in case of secondary account
-Check whether company details are provided in cases of company's current account
-Check whether proofs for joint account is provided in case of joint account
-Check whether you are able deposit an account in the name of either of the person in an joint account.
-Check whether you are able withdraw an account in the name of either of the person in an joint
account.
-Check whether you are able to maintain zero balance in salary account
-Check whether you are not able to maintain zero balance (or mini balance) in non-salary account.
viva questions
1. Can you explain boundary value analysis?
2. Can you explain equivalence partitioning?
3. Can you explain random/monkey testing?
4. What are semi-random test cases?
5. What is negative and positive testing?
6. How did you define severity ratings in your project?
 Test plan document for library application
The Library Management System is an online application for assisting a librarian in managing a book
library in a University. The system would provide basic set of features to add/update clients, add/update
books, search for books, and manage check-in / checkout processes. Our test group tested the system
based on the requirement specification.
INTRODUCTION
This test report is the result for testing in the LMS. It mainly focuses on two problems: what we will
test and how we will test.
Result
GUI test
Pass criteria: librarians could use this GUI to interface with the backend library database without any
difficulties
Result: pass
Database test
Pass criteria: Results of all basic and advanced operations are normal (refer to section 4)
Result: pass
Basic function test
Add a student
Pass criteria:
• Each customer/student should have following attributes: Student ID/SSN (unique),
Name,Address and Phone number.
• Result: pass
• The retrieved customer information by viewing customer detail should contain the four
attributes.
• Result: pass
Update/delete
studentPass
criteria:
• The record would be selected using the student ID Result:
pass
• Updates can be made on full. Items only: Name, Address, Phone number Result: pass
• The record can be deleted if there are no books issued by user.
Result: Partially pass. When no books issued by user, he can be deleted. But when there
arebooks Issued by this user, he was also deleted. It is wrong.
• The updated values would be reflected if the same customer's ID/SSN is called for.
Result: pass
• If customer were deleted, it would not appear in further search queries.
Result: pass
Add a book
Pass criteria:
• Each book shall have following attributes: Call Number, ISBN, Title, Author name.
Result: pass
• The retrieved book information should contain the four attributes.
Result: pass
Update/delet
e bookPass
criteria:
• The book item can be retrieved using the call number Result:
• did notpass. Can not retrive using the call number
• The data items which can be updated are: ISBN, Title, Author name Result: pass
• The book can be deleted only if no user has issued it.
 • Result: partially pass. When no user has issued it, pass. When there are user having issued
it,did not pass
• The updated values would be reflected if the same call number is called for Result: pass
• If book were deleted, it would not appear in further search queries. Result: pass
Search for book
Pass criteria:
• The product shall let Librarian query books„ detail information by their ISBN number or
Authoror Title.
Result: pass
• The search results would produce a list of books, which match the search parameters
withfollowing Details: Call number, ISBN number, Title, Author Result: pass
• The display would also provide the number of copies which is available for issue Result: pass
• The display shall provide a means to select one or more rows to a user-list Result: pass
• A detailed view of each book should provide information about check-in/check out status,
withthe borrower„s information.
Result: pass
• The search display will be restricted to 20 results per page and there would be means to
navigatefrom sets of search results.
Result: pass
• The user can perform multiple searches before finally selecting a set of books for check
in orcheckout. These should be stored across searches.
Result: pass
• A book may have more than one copy. But every copy with the same ISBN number should
havesame detail information.
Result: pass
• The borrower„s list should agree with the data in students„
accountResult: pass
Check-in book
Pass criteria:
• Librarians can check in a book using its call number
Result: pass
• The check-in can be initiated from a previous search operation where user has selected a
set ofbooks.
Result: pass
• The return date would automatically reflect the current system date.
Result: did notpass.
• Any late fees would be computed as difference between due date and return date at rate of
10cents a day.
Result: did not pass
• A book, which has been checked in once, should not be checked in again
Result: pass
Check-out book
Pass criteria:
• Librarians can check out a book using its call number
Result: pass
• The checkout can be initiated from a previous search operation where user has selected a set of
books.
Result: pass
• The student ID who is issuing the book would be entered\
Result: pass
• The issue date would automatically reflect the current system date.
Result: did notpass
 • The due date would automatically be stamped as 5 days from current date.
Result: did notpass
• A book, which has been checked out once, should not be checked out again Result: pass
• A student who has books due should not be allowed to check out any books
Result: did notpass
• The max. No of books that can be issued to a customer would be 10. The system should not
allowcheckout of books beyond this limit.
Result: pass
View book detailPass criteria:
• This view would display details about a selected book from search operation
Result: pass
• The details to be displayed are: Call number, IBN, Title, Author, Issue status (In library
orchecked out), If book is checked out it would display, User ID & Name, Checkout date, Due
date
Result: for checkout date and due date, did not pass
• Books checked in should not display user
summary.
Result: pass
• Books checked out should display correct user details.
Result:pass
View student detail
Pass criteria:
• Librarians can select a user record for detailed view
Result:pass
• The detail view should show:
a.User name, ID, Address & Phone number
Result: pass
b. The books issued by user with issue date, due date, call number, title
Result: did not pass
c. Late fees & Fines summary and total
Result: did not pass
•The display should match existing user profile
Result:pass
• The books checked out should have their statuses marked
Result: pass
• The book search query should show the user id correctly.
Result: pass
Network test
Pass criteria: Results of operations (ping, ftp and ODBC connectivity check) are normal
Result: did not test this item, because no enough machines and no available
environment.
Viva questions
1. How to create a test plan document for Library Management System?
2. what is object repository
3. How many test cases can u write
1) File - open dialog box in notepad please write if software failed in customer environment what we
called a) error b) fault c) defect d) failure
4.What test plan should contains?
5. What is test strategy?
6. Define test Plan? What is the difference between Master Test Plan and Test Plan?