1.

Identify system specification and design test cases for

purchase order Management.
VAns. :

TC_Id| TC_Name Steps Input Data Expected Result Actual Result Status

TC 01 Item name Enter item name in alphabets pass

"prd1" Product name should| Accepting
be accepted
TC 02 Quantity Enter item name in number pass
20 Product quantity should |Accepting
|beaccepted
TC _03| Item_CatEnter item name in alphabets "prd1" Product name should | Accepting pass

be accepted
TC_04 Submit Click on submit button |Itshould go to next page It is going to next page pass

TC_05 Cancel Click on cancel button |It should remain on It is remaining on the Pass

same page same page

2. Identify system specification &design test cases for Inventory management.

Ans. :
Expected Result Actual Result Status
TC_Id TC_Name Steps Input Data
|Product name should be Accepting pass
TC_01 Item name Enter item name "prd1"
|inalphabets accepted
pass
Enter item name 1000 |Product quantity should beAccepting
TC_02 Quantity
available in number accepted
pass
Enter item name "prd1" Product name should be|Accepting
|TC_03 Item_Cat
in alphabets accepted
It isgoing to next page pass
Submit Click on submit It should go to next page
TC_04
button
same Pass
Click on cancel It should remain on same| It is remaining on the
TC_05 Cancel
page |page
button
3. Design test cases for simple calculator application. (BB Testing)
M Ans.:

No. Test Test case Prerequisite Steps Input Expected Actual Remarks
Result
Case-ID Objective
data Result /Status
|Calculator is1. Key in a valid| 135 +100|235(addition. 235 Pass
1 TC_1 To add two
integer and |switched on integer from above ten digits
display the 9999999999 to will be expressed
result on ten + 9999999999 in exponential
|digit calculator |2. Key in operator+
form)

|3. Key in second

operand, a valid
integer from
9999999999 To
+ 999999999

2 TC_2 To subtract Calculator is1. Key in a valid| 135- 100 35(subtraction, 35 Pass
two integer switched on integer from above ten digits
and display the 9999999999 to will be expressed
result on ten + 9999999999 in exponential
digit calculator form)
2. Key in operator -
3. Key in second
operand, a valid
integer from
- 9999999999 To
+999999999

3. TC_3 |Tomultiply Calculator is 1. Key in a valid| 100 x 40040000 40000 Pass

two integer switched on integer from |(multiplication,

and display the - 9999999999 to above ten digits
result on ten +9999999999 will be expressed
| digit calculator 2. Key in operator x
|in exponential
form)
3 Key in second
operand, a valid
integer from
- 9999999999 To
+999999999
No. Test Expected Actual Remarks
Test case Prerequisite Steps Input
Case-ID Result Result /Status
Objective data
4. TC_4 40(division above 40 Pass
To divide two Calculator is1. Key in a valid 1007 2
|integer and switched on integer from ten digits will be
adisplay the 9999999999 to
expressed in
result on ten +9999999999
exponential form)
digit calculator
o2. Key in operator /
3. Key in second
operand, a valid
integer from
- 9999999999 To
+999999999.

5 TC_5 To clear the Calculator is Press C Symbol _0* Symbol Pass

Screen switched on should appear on 0*
Screen appear s
on
Screen

6 TC_6To delete Calculator is Press <- (backspace) One Digit should One Pass
be deleted from Digit is
|digitsone by switched on
one
right hand side deleted
from
right
handside

4. Design test cases for railway reservation form

V Ans. :
Test case Input Data Expected Result Actual Result Status
Test
Case Id Objectives
Login field Any valid login nameIt should accept the The login name is accepted Pass
TC_I
(abcd xyz) login name

TC_2 Password field Valid password Valid password Successful login message Pass
should be accepted

TC_3 Password field Invalid password Should not accept Message displayed as Invalid| Pass
Wrong password login or wrong password

TC_4 Date of journey Date format not before It should accept Accepted Pass
the current date

TC_5 Date of return Date greater than the It should accept date Accepted Pass
journey return journey date
5. Design test cases for e-commerce (Flipkart, Amazon) login form
MAns.: Actual Result
TC Id TC_name Steps Input data Expected Status
result
in"abc123" It should accept It is accepted Pass
TC_01 User Enter the username
usermame
name alphanumeric alphabets A-Z the username
Number 0-9
It should accept| It is accepted Pass
TC_02 Password | Enter the password in"abc123" password
alphanumeric alphabets A-Z. the password
Number 0-9
It should goes It is going to next Pass
TC_03 Submit 1. After valid username and
password to next page page
2 Click on submit button
should It shows login page Pass
It
TC_04 Cancel Click on cancel button
with blank fields
remain in login
page with blank
fields

6. Design test cases for Web Pages Testing any Web Sites
Ans. :
Expected result
Test status Req. Ref. Page/Area Scope
ANONYMOUS
Scenario: User views and clicks verify content /design.
Ready 1838-1 Homepage on header links. main nav and dropdown links
desktop
Actions : take
user to those sections.
1. Click on logo
2. Click main nav
register link takes user to
(navigation links) links and registration page.
search takes user to
dropdowns.
search/results
3. Click on Register link.
page.
4. Click on magnifying glass
icon.
5. Enter a search term and
submit.
Scenario : User views carousel verify conten/design
Ready 1838-2 Homepage carousel auto-rotates
desktop hero's.
Test Conditions : user can manually rotate by
1 View autorotation. selecting arrow (page needs to be
refreshed to go back to
2 Click on arrows to manually
rotate. autorotation)
3. Click on links within each carousel marker (black bar under
side moves location to the right
slide.
to represent each slide)
verify all links.
7. Write program and design test cases for the
following Control and decision
statement.
making do

1) For... Loop printf(t%d"i);:

2) Switch...case it+;

3) Do...While }while(i< =n);

4) If...else
ZAns. :
else
Program in C
printf(n Invalid number");
#include <stdio.h> printf("n Enter anumber l to 3 :";
#include <conio.h>
switch (k) ;
{
main() case l:

printf("One);
int n,i.k ; break;
i= l; case 2:

printf("Two "):
printf(n Enter a number upto 10:"; break;
scanf("d"&n); case 3:

printf("Three "):
if(n<=l0) break;
{ default;
while(i<=n) printf("Invalid'");
{
printf("d".): eetcht);
i++;

i=l;
printf("nin);
 TC_Name Steps Input Expected Result Actual
Pradica
Data Result Slatux
TC_01 If Enter 5 Number should Acepting
number be accepted pass
10

TC_02 Else Enter 20 Go in else part Shifting in

number >= else part pass
10

TC_03 Print 1 to5

For Enter 5 Printing 1to 5 pass
number <=
10

TC_04 Do_while Enter Print 1 to5 Printing I to 5 pass

number <=
10

TC_05 Switch_case Enter 2 Two Two

pass
number
1-3

8. Prepare test plan for an identified Mobile project specification, budget and customer's
application. requirements.
V Ans. : 1.3 References

1. Introduction This section contains the documents which

support test
1.1 Overview
plan and can be referred during the testing process.
Commonly, among them are :
A Test Plan is a document which describes a
scope of project plan
testing, test strategy, objectives, effort, schedule and
resources required. Its main purpose is to guide the system requirements
whole testing process and used mostly by Project specification design documentation.
Managers or Tests Engineers. The example of 1.4 Acronyms and Abbreviations
Functional Test Plan you can find here.
All the acronyms which are used in Test Pan are
1.2 Scope
explained and described. For example,
The scope of work is defined at the beginning of the DDD - Database design document
testing process. A project team should clearly
QMS - Quality Management System
understand what features and functions to be tested and
SLC - Software life cycle.
which ones are out of scope. To determine the scope of
testing a Manager must take into consideration the
 2. Test Plan and Strategy
2.2.2 Testing Procedure
2.1 Unit Testing -

test cases preparation

2.1.1 Objective test executions

The main objective of unit testing is to verify whether bug reporting.

every single unit operates as intended. For a separate 2.2.3 Types of System Testing
unit, an engineer can take a function, procedure or
2.2.3.1 Performance Testing
method. Sometimes, it can even be the whole module
of the Performing testing is conducted to detect issues related
application. Unit testing can be conducted
to:
manually, but more often automated testing is applied.
memory consumption
2.1.2 Entry Criteria
power utilization
planning phase has been finished network connectivity
testable units are available operating in the background
all functional requirements have been defined switching between applicationse ass
a unit testing environment has been set up. memory leakage.

2.1.3 Exit Criteria 2.2.3.2 Interrupt Testing

As far as mobile devices have a huge range of
all planned test cases have been covered
functions, the work of the application may be
allthe bugs found have been reviewed interrupted by various reasons, e.g., an upcoming call,
performance of key modules has been tested. message, other apps notifications, mail, low memory
warning, inserting a cable, etc. The application should
2.1.4 Logging Tests and Reporting be suspended and afterward launched from the place it
was stopped without losing unsaved data.
Developers fix the defects found in each unit. If these
defects are related to other modules and units, they 2.2.3.3 Usability Testing
must be reported.
Usability testing is applied to check whether the
2.2 System Testing application is easy to use and understand from the
user's point of view.
2.2.1 Objective
2.2.3.4 Installation and Launch testing
System testing is generally conducted after Unit
Testing. The objective of System Testing is to evaluate During installation testing, an engineer checks whether
compliance of an integrated application with its there are any issues during the installation,

requirements. During this stage engineers usually uninstallation, and updating of the application. Once
encounter issues which appear when the system has the application has been installed, an engineer checks
been integrated. launching process. The application must be loaded
quickly and correctly. Closing the application should
not require much time as well.
 4. Risks and ASSump
2.2.3.5 Functional Testing
4.1 Risks
All the functions and features of the application are
tested to verify whether they operate according to the The following risks exist while testing a
specification. application :
mobile
2.2.3.6 Security testing availability of devices
new features and moodification which
Security testing is conducted to find the application have not
vulnerabilities and prevent private data losses. been planned in advance

2.2.3.7 Regression testing changes in requirements

delays in schedule.
Regression testing is a re-execution of tests that had
been done before the code changes. Its purpose is to 4.2 Assumptions
verify whether a new functionality has affected the
each release is accompanied by a note with information
existing one. It is also conducted after a new product
release.
about implemented features and their impact on the
system
2.3 Pass/Fail Conditions
all "bugs-blockers" receive high priority
All the conditions when tests pass or fail are defined all the bugs found are fixed before the next software
and described. release

2.4 Test Report all documents are up-to-date and delivered to the
testing team in time
Test Report helps to summarize testing activity in a
formal way. It should contain : all necessary equipment and tools are provided and
ready for testing
application name and overview
tests schedule is reviewed in case there are any
testing hardware and software environment
obstacles for testing activity.
the number of tests cases executed/passed/failed.
5. Entry and Exit Criteria
For each issue that has been encountered, the following
information is provided: 5.1 Entry Criteria

bug description development phase has been finished

bug status (open, fixed, etc.) requirements have been defined and approved
bug location test design and tests plan have been created
test environment has been set up
steps to reproduce an issue.
all necessary resources are available.
3. Schedules for Testing
5.2 Exit Criteria
A test schedule is elaborated by Project Managers and
tests cases are executed
helps to monitor the testing process.
the rate of tests cases passed is satisfactory, e.g. 95%
failed test cases are not related to crucial functionality
 tests results have been accepted 9. Deliverables
critical defects have been fixed.
The list of testing deliverables usually contains :
6. Test Metrics
tests plan
Test metrics are quantitative measures which help to test cases documents
estimate the testing effort. The most common metrics are : test strategy
requirement coverage test results
test cases coverage test summary report.
number of tests executed 9. Design test plan and test cases for Notepad (MS
number of defects found (taking into consideration Window based) Application.
their priorities and severities) V Ans. :
tests design effort Following are test scenarios for notepad or any other
total test effort. basic text editor.

7. Logging Tests and Reporting Verify that on launching the notepad application, the
notepad editor should open with its default size.
Each found issue should be properly reported using
Verify that user can write/type alphabets from a
special tools and applications.
standard keyboard.
8. Roles and Responsibilities Verify that user can type numerics from a standard
Roles and responsibilities on the project must be clearly keybaord
defined and divided among the project stuff. Verify that user can type special characters and
Commonly, the roles are as follows : symbols on notepad editor window.
Verify that by default the font size is normal or as per
8.1 Project Manager
the specifications.
Project Manager is responsible for managing the whole Verify that user can set the font size and family.
testing process. He/she approves all test documentation, Verify that user can save the text in a file.
considers budget and time terms, and provides
Verify that user can open any exiting file in notepad.
necessary resources.
Verify that file formats not permitted by notepad are
8.2 Test Lead
not loaded and doesn't corrupt the application.
Test Lead is responsible for collecting requirements, Verify that user can append textt to any file and again
planning process, test activity monitoring and project save the file.

reporting. Verify that user can select, copy and paste text.
8.3 Test Engineer Verify that user can select, cut and paste text.
Test Engineer is responsible for tests case preparation Verify that user can select and delete a text.
and execution as well as issue reporting. Verify that user can delete a text using backspace and
delete buttons.
 Verify that user can navigate through the text in file We can write number of test cases on notepad
using the arrow keys. application. The basic concept is to validate menu :
Verify that user can navigate through the text in file 1) File 2) Edit
using mouse pointer. 3) Format 4) View
Verify that user can edit and delete data in between the
5) Help
text file.
Each of these menu has submenu.
Verify that user can undo any latest change done in file.
For Menu: Validate the click of each menu
Verify that user can redo any change undone by undo corresponding to relevant result. Say if you open file
option. menu and hit on new, the notepad should open blank
Verify that user can search for single or multiple file and cursor blinking on the top right corner.
characters and words through the file.
E.g.: test case
Verify that user can search and replace single or Test case No. : TXXXX
multiple characters and words through the file.
Test scenario : Validating menu option
Verify that user can resize the notepad window.
Expected Result : if file menu is opened and hit on
Verify that user can minimize the notepad editor new, the notepad should open blank file and cursor.
window.
Actual Result : Notepad successfully opened new file.
Verify that user can maximize the notepad editor
Similarly we can validate for submenu and other
window.
menuS.

Verify that user can close the editor window by

clicking the cross icon.

TC_Id TC_Name Steps Input Data Expected Result Actual Result Status

TC_01 New 1. Open application New blank file must beOpening New pass

t2. Click on File Menu opened Files

3. Select :New" menu

TC_02Open |1. Open application File location and Existing selected file|Opening pass

Click on File Menu File name should be opened selected File

2.

3. Select "Open" menu and

browse required file

TC_03|Save Click File ’ Save File location and| Existing file must beSaving selected pass
File name saved File

TC_04 Exit Click File ’ Exit Exit from editor Exiting from pass
editor
 10. Prepare defect report after executing test cases for library management system.
Ans.:
ID Lbl

Project Library Management

Release Version 1.1

Module Book_ed
Detected Build Version Bel

Summary Book edition is not accepting alphanumeric values

Description Only alphabets are accepted, not numbers
Steps to Replicate Enter - alphanumeric value
Actual Result Error

Expected Results Should be accepted

Attachments Bvjpg
Remarks Must accept alphanumeric value
Defect Severity
Defect Priority Pr-29

Reported By Mr. Kunal B.

Assigned To Mr. Rahul S.

Status Ss001

Fixed Build Version 1.0A

11. Prepare defect report after executing test cases for Withdrawn of amount from ATM Machine.
VAns. :
ID A1

Project ATM

Release Version 1.1

Module Withdraw

Detected Build Version W1

Summary Not accepting amount greater than 10000

Description Bank allows upto 25000 at a time

Steps to Replicate Entered mount above 10000

Actual Result Error

 ID A1

Expected Results Should be accepted

Attachments
Atml.jpg
Remarks Must accept value upto 25000
Defect Severity
Defect Priority Pr-14

Reported By Mr. Kunal B.

Assigned To Mr. Rahul S.

Status Ss001

Fixed Build Version 1.0A

12. Prepare defect report after executing test cases for any
login form.
Ans. :
ID L1

Project Login Form

Release Version 1.1

Module Login
Detected Build Version LI

Summary Accepting blank user name

Description Should not accept blank value for user name

Steps to Replicate Entered blank value

Actual Result Accepted

Expected Results Should not be accepted
Attachments lgl.jpg
Remarks Please check

Defect Severity
Defect Priority Pr-56

Reported By Mr. Kunal B.

Assigned To Mr. Rahul S.

Status Ss001

Fixed Build Version 1.0A

13. Design and run test cases for WordPad (MS
Windows based), Using an Automated toul.
Ans. :
TC ld| TC Name
Steps Input Data Expected Result Actual Result Status
TC_01 New |1. Open application New blank file must beOpening New pass
2. Click on File Menu File
opened
3. Select "New" menu
TC_02|Open 1. Open application File location and Existing selected fileOpening pass
2. Click on File Menu File name should be opened selected File
3. Select "Open" menu and
browse required file
TC_03 Save Click File ’ Save File location and Existing file must be Saving selected pass
File name saved File
|TC_04Exit Click File ’ Exit Exit from editor Exiting from pass
editor

14. Design and run test cases for MS Word application using an
Automation Tool.
V Ans.:
TC_Id|TC_Name Steps Input Data Expected Result Actual Result Status
TC_01 New 1. Open application New blank file must|Opening New File pass
2. Click on File Menu |be opened
3 Select "New" menu

TC_02 Open 1. Open application File location Existing selected|Opening selected File pass
2. Click on File Menu and File name file should be opened
|3. Select "Open" menu
and browse
required file

TC_03 Save Click File ’ Save File location |Existing file must be Saving selected File pass
and File namesaved

TC_04|Exit Click File Exit Exit from editor |Exiting from editor pass

Lab Ends..