The objective of this assignment is to familiarize yourself with the thought process that goes into the creation, development and documenting of unit test cases. In this assignment, you will be told about a function that has been developed which you need to create a number of test cases for … sounds simple – right?!?
This is a partner-based assignment and you can have partner if you wish.
This assignment supports the following course outcomes:
- Discuss the importance of properly specifying testing procedures in order to ensure software quality
- Please refer to the SET Policies document regarding Academic Integrity Information
- Please refer to the SET Policies document regarding Late Policy
Please refer to the assignment weighting in the Instructional Plan for the course as well as the assignment’s Rubric in the course shell.
Review Module-05 (Part 1)’s content on the components of the “Sean’s Way” style of documenting a unit test case as well as the types of tests (functional, exception, etc.) Pay close attention to the various sections of the unit test description and what content to place there.
Let’s pretend that you’ve have been given the task of creating and writing unit test cases for a function (called Bazinga()) that is found within a system that your company is developing. In order to develop test cases, you know that you must familiarize yourself with the internal workings and expectations of the function. So you need to read the SRS and also read any design documentation that tells us what Bazinga() is supposed to do. From what you read – you extract the following set of requirements which help you understand that Bazinga():
- Review the types of tests from Module-05 (Part 1) in the course content – specifically looking at the functional, exception and boundary types of tests
- Review the “Sean’s Way” style of documenting your test cases material from that module (slides 20, 21 and 47, 48)
- Please note that unit test cases are presented in tabular format (as shown on slide 48)
- I want you to create 4 functional test cases, 4 exception test cases and 2 boundary test cases for the Bazinga() function
- NOTE: You might want to review the ideas presented on slides 31 through 33
- I want you to document your unit test cases using the Sean’s Way style of documenting test cases and create a Test Specification
- In the end, your Test Specification should have:
- An Introduction section (a major section) which tells the reader about the Bazinga() function, what it does and how it does it … give this information in your own words.
- Ten (10) test cases laid out in the recommended test case documentation style
Please have major sections in your report which separate the different types of tests
- So you should have a Functional Tests section, an Exception Tests section, etc.
Place your work in a document titled “Bazinga Unit Test Specification”. This document should be produced and written in compliance with the SET Reporting Standards.
- You do not need a Revision-History in your report
- In terms of citations (References) for this report – think about the sources ofinformation that you are drawing ideas and guidelines from
- If you are working with a partner, ensure that both of your names are on the report title page. Only one member of the team needs to submit to the drop-box
- Your report must be submitted in either Microsoft Word or PDF format.