Software Testing and Documentation

Running head: SOFTWARE TESTING AND DOCUMENTATION
Software Testing and Documentation
Name of the Student
Name of the University
Author Note

1SOFTWARE TESTING AND DOCUMENTATION
Question 1: Real software failure
In the year of 2014, exam takers throughout the nation of United States were rendered
helpless in uploading his or her respective exam files. This generate wide scale panic
concerning the blowing states possibility and uploading deadlines. The incident generated
from a failure in the ExamSoft’s Examplify application.
At the very starting day of bar exams, these exam takers had to suffer the ordeal of
largescale outages of the Examplify application portals built by ExamSoft, that started
causing delays of exams in multiple regions (Casey, Casey and Griffin 2018). Countless
number of the bar candidates had to stay wide eyed while worrying about the times they tried
to begin writing their essays as well as how the exemplify kept failing preventing them from
being able to submit their work at all. All of this began when ExamSoft released a series of
updates for their application on days leading to the exams.
Hence to prevent such software failures from paralyzing academic work, conducting
exams as well as operations of various associated businesses, it is of prime importance to get
have software testing conducted on software applications before rolling out any changes to
them live through automatic updates. As a result, for the application MTEST which is to
automate grading of student answers needs to be tested as per the requirements identified.

2SOFTWARE TESTING AND DOCUMENTATION
Question 2a: Identification of Test Cases
Test case design for the Marking and grading application MTEST has been conducted
with the help of multiple testing techniques (Mahmoud et al. 2019). These techniques are
equivalence class partitioning, boundary value analysis as also error guessing and negative
testing with respect to the requirements of the application (Fögen and Lichter 2018). The test
cases identified are listed below.
List of identified test cases for the marking and grading software application MTEST are:
1. Verify error message for empty data in input record of title
2. Verify acceptance of valid title records
3. Verify error message for negative integers present in No. of questions column
4. Verify error message for value '0' in No. of questions column
5. Verify values within the range 1-999 are getting accepted
6. Verify error message for numbers more than 999 in columns 1-3
7. Verify error message if first record set is empty
8. Verify acceptance if one question present
9. Verify acceptance of second record for 51-100 questions
10. Verify acceptance of third record for 101-150 questions
11. Verify error message for columns 1-9 if empty
12. Verify acceptance of student data in columns 1-9
13. Verify error message if student answers exceed number of questions