Test Case Identification for MTEST: Grading Application Analysis

This assignment provides a comprehensive analysis of test case identification for the MTEST grading application. It details the application of various software testing techniques, including negative testing, boundary value analysis, equivalence class testing, and error guessing. The solution outlines specific test cases designed to verify different aspects of the application, such as input file validation, error handling for various scenarios (e.g., total questions, unrecognized student names), and execution of different question ranges. The analysis highlights the importance of boundary value analysis in identifying potential defects and the role of error guessing, emphasizing the need for experienced testers. The assignment also includes a detailed list of references to support the methodology and findings.

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

1TEST CASE IDENTIFICATION FOR MTEST
Question 1: Identification and listing of test cases for MTEST grading
application
Various software testing techniques were used to identify the test cases for the
application MTEST (Barr et al., 2015). The testing techniques are negative testing, boundary
value analysis, equivalence class and error guessing tests and were chosen based on the
requirements of MTEST marking application (Tian et al. 2018). The test cases identified in
the test design are:
i. Verify that accepted title record has contents
ii. Verify error message for inout files with empty title
iii. Verify that error check for total questions equalling 0
iv. Verify that error check for total questions equalling 1000
v. Verify that execution of total questions equalling 1
vi. Verify that execution of total questions equalling 999
vii. Verify first record between columns 10 and 59 have data for 1 to 50 questions exams
viii. Verify second record between columns 10 and 59 have data for 51 to 100 questions
exams
ix. Verify third record between columns 10 and 59 have data for 101 to 150 questions
exams
x. Verify execution of input files with student data in columns 1 to 9
xi. Verify that error check for unrecognized student names in columns 1 to 9
xii. Verify that execution for values 2 and 3 in column 80 of question and student record
Question 2: Test Cases based on Boundary Value Analysis
Boundary value analysis or BVA is the testing technique that involves testing with
boundary values regarding valid as well as invalid equivalence class partitions of a particular

2TEST CASE IDENTIFICATION FOR MTEST
software (Agushinta, Jatnika and Medyawati 2019). Application behaviour near these
boundaries are typically erroneous and hence the testing is conducted with these boundary
values for identifying defects.
The test cases following the boundary value analysis technique are:
 Verify that error check for total questions equalling 0
 Verify that error check for total questions equalling 1000
 Verify that execution of total questions equalling 1
 Verify that execution of total questions equalling 999
Here the boundary values are identified to be 0, 1000, 1 and 999. This is because MTEST
only supports 1 to 999 questions.

3TEST CASE IDENTIFICATION FOR MTEST
Question 3: Test Cases based on the Error Guessing technique
Error guessing refers to the testing technique where guesses are made on where and
how the application may faulter for a given function (Hooda and Chhillar 2015). In such kind
of testing techniques, the parts of the application that is more likely to cause errors are
factored in. After which the tester designs the test cases based on the identified factors. For
this comprehensive testing experience is required among testers and test analysts so that the
most defects can figured out. Tacit knowledge of the tester therefore plays a critical role here.
Test cases based upon the error guessing technique are as follows -
 Verify that error check for unrecognized student names in columns 1 to 9
There was no separate requirement for such a test but prior experience of the tester suggested
this test to be factored in.

4TEST CASE IDENTIFICATION FOR MTEST
References
Agushinta, R.D., Jatnika, I. and Medyawati, H., 2019, March. Boundary Value Analysis
Testing on Augmented Reality of Indonesian Fruit Recognition at Mekarsari Tourist Park
using Cloud Method on Android Mobile Devices. In Journal of Physics: Conference Series
(Vol. 1196, No. 1, p. 012060). IOP Publishing.
Barr, E. T., Harman, M., McMinn, P., Shahbaz, M., & Yoo, S. (2015). The oracle problem in
software testing: A survey. IEEE transactions on software engineering, 41(5), 507-525.
Hooda, I. and Chhillar, R.S., 2015. Software test process, testing types and techniques.
International Journal of Computer Applications, 111(13).
Tian, Y., Pei, K., Jana, S. and Ray, B., 2018, May. Deeptest: Automated testing of deep-
neural-network-driven autonomous cars. In Proceedings of the 40th international conference
on software engineering (pp. 303-314). ACM.