Software Engineering (22413)

Experiment No 9
Write test cases to validate requirements of assigned project from SRS document.

I Practical Significance

A test case is a specification of the inputs, execution conditions, testing procedure, and
expected results that define a single test to be executed to achieve a particular software testing
objective, such as to exercise a particular program path or to verify compliance with a specific
requirement.

II Relevant Program Outcomes

All POs are listed.

III Relevant Course Outcomes

Study SRS document and designing test cases.

IV Practical Learning Outcomes

Detailed description of all aspects of the project to be built with test case design.

V Practical Skills
Deeper understanding of System Requirement Specification of a software system, test cases formulation
strategy.

VI Minimum Theoretical Background

A Test Case is defined as a set of actions executed to verify a particular feature or functionality
of the software application. A test case is an indispensable component of the Software Testing LifeCycle
that helps validate the AUT (Application Under Test).

Test scenarios are rather vague and cover a wide range of possibilities. Testing is all about being
very specific.

VII Resources required

Sr No Instrument Specification Quantity Remarks

Any Desktop PC
1 Computer System with attached 10 No. Whichever is available
HardDisk
2 Any UML Software - 1 No. -

Marathwada Mitra Mandal’s Polytechnic,Thergaon.

Software Engineering (22413)

VIII Procedure

1. Detailed study of the System under test

2. Written in simple language
3. Use Test case template

IX Precautions

1. Change the requirement carefully.

2. Save changes if required under the guidance of teacher.

X Description

Test case template

It looks like:

i) Test Case ID: This field is defined by what type of system we are testing. Standard rules are as follows:
 If we are making test case for a general application which doesn’t belong to any specific module then
ID would start as TC001.
 If we are making test cases for a module specific system then ID would start from MC001.
 If test case has more than one expected result then we make it as version number wise. E.g. TC001.1,
TC001.2 etc. All these test cases are sub part of TC001.

ii) Test Case Name: This filed can contain

 Name of the feature you are testing
 Requirement number from the specifications
 Name of a particular Button or input box
 Requirement name as classified in client’s document

Marathwada Mitra Mandal’s Polytechnic,Thergaon.

Software Engineering (22413)

The main advantage of maintaining this field is, if a requirement gets changed in future then we can
easily estimate how many test cases that change will affect and we change/remove the corresponding
test cases accordingly.

iii) Description: This field has the summary what respective test case is going to do. It explains what
attribute is under test and under what condition. E.g. If a text box is under provigil online test, which
allows only number and alphabets then description can be written as “Random special characters (@, #,
%,$,^,*) are entered”, if we want to test a negative scenario.

iv) Pre-Conditions: when the system needs to be in a particular base state for the function to be tested,
these pre conditions should be defined clearly.
Pre-conditions could be:
 A certain page that a user needs to be on
 A certain data that should be in the system
 A certain action to be performed before “execution steps” can be executed on that particular
system.
Pre-conditions should be satisfied before the test case execution starts.

v) Execution steps: These are the steps to be performed on the system under test to get the desired
results. Steps must be defined clearly and must be accurate. They are written and executed number
wise.

vi) Expected Results: These are the desired outcomes from the execution steps performed. Expected
results should be clearly defined for each step. It specifies what the specification or client expects from
that particular action.

vii) Actual result: This field has the actual outcomes after the execution steps were performed on the
system under test. If the results match with the expected ones then we can j ust write “As expected”,
otherwise we need to mentioned the exact result observed.

viii) Status: This field can have following values based on the actual result we got, they are:

 “Passed” – The expected and actual results match

Marathwada Mitra Mandal’s Polytechnic,Thergaon.

Software Engineering (22413)

 “Failed”- The actual result and expected result do not match

 “Not tested”- The test case has not been executed
 “Not Applicable”-The test case does not apply to the feature any more since the requirement
changed or modified
 “Cannot be tested” – This may be because precondition is not met. There could be a defect in one of
the steps leading up to the function under test.

ix) Comments: This column is for additional information. So for e.g. if status is set to “cannot be tested”
then tester can give the reason in this column.

Fig: sample test case to login form of Twitter social site.

Marathwada Mitra Mandal’s Polytechnic,Thergaon.

Software Engineering (22413)

XI Practical related Questions

1. Prepare six test cases for home page of marketing site www.flipkart.com.

Ans:

Marathwada Mitra Mandal’s Polytechnic,Thergaon.

Software Engineering (22413)

2. What are types of test report? Write contents of test summary report.
Ans:
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....

Marathwada Mitra Mandal’s Polytechnic,Thergaon.

Software Engineering (22413)

………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....
………………………………………………………………………………………………………………………………………………….....

Marathwada Mitra Mandal’s Polytechnic,Thergaon.

Software Engineering (22413)

3. Write important six test cases for the ‘Login Form’ of the Facebook website.
Ans:

Marathwada Mitra Mandal’s Polytechnic,Thergaon.

Software Engineering (22413)

List Of Student Team Members:

1. …………………………………………………………………………………………………
2. …………………………………………………………………………………………………
3. …………………………………………………………………………………………………
Marks Obtained Signature Of
Teacher
Process Product Total (25)
Related(15) Related(10)

Marathwada Mitra Mandal’s Polytechnic,Thergaon.