Test Case Identification for Mtest

Running head: TEST CASE IDENTIFICATION FOR MTEST
Test Case Identification for Mtest
Name of the Student
Name of the University
Author Note

1
TEST CASE IDENTIFICATION FOR MTEST
Question 1: Real world example of software failure
Various factors can lead to software failures. These factors can be - upgrading of
applications without ensuring changes regression testing and retesting of the software after
the changes (Harman, Jia & Zhang, 2015). Security of a software also plays an important
role. Applications with vulnerabilities present are easier to exploit (Briand et al, 2016). Bugs
and glitches of software applications lead to inaccurate outcome from the software.
A major security flaw got discovered by an international airline which would allow
anyone having computers with the valid URLs in accessing and manipulating the boarding
passes of passenger flights. The software was a mobile boarding system called TSA. Though
this flaw got timely addressed by the airline and have denied customer data getting
compromised, alarming questions arose from this issue regarding security of data with air
travel becoming more and more dependent on software applications in managing all the
complexities involved.
Here the prompt action of the airline in notifying the vendor helped in resolving the
issues with the fix immediately being released so that the bug cannot get exploited any
further. The fix ensured that the software checked all the several layers of security which
prevents customers from making use of boarding passes that were not theirs’. Since the
duration of the failure was very short, the incident did affect the aviation industry by much.

2
TEST CASE IDENTIFICATION FOR MTEST
Question 2: Identifying the test cases according to the scenarios created
based on requirements of the software
The software testing techniques that have been used to identify the test cases for
MTEST are boundary value analysis, equivalence class partitioning, negative test cases and
error guessing test cases (Garousi & Mäntylä, 2016). The list of test cases are given in the
table below.
MTEST Test Case Design
Test Case_ID Scenarios Test Cases
MTC1001
Validate that
record set for
Title contains
data
Verify that title
MTEST accepts
title record set
with data
MTC1002
Validate that
record set for
Title contains
data
Verify error for
input files
having vacant
title records
MTC1003
Validate
question count
is between 1
and 999
Verify that
error code
present when
question count
equals 0
MTC1004
Validate
question count
is between 1
and 999
Verify that
error code
present when
question count
equals 1000
MTC1005
Validate
question count
is between 1
and 999
Verify that
input files with
question count
1 gets
executed
MTC1006
Validate
question count
is between 1
and 999
Verify that
input files with
question count
999 gets
executed