Community partners are invited to present either a specification-based or code-based testing challenge, the criteria for each are listed below:

SPECIFICATION-BASED:

Students will learn specification-based unit testing methods including the use of equivalence class, boundary value and decision table. As part of the students learning, a community partner provides a document containing the specification of a project (i.e., the specification of a unit or a couple of units) and students are asked to prepare a document including a set of test cases that they think are required to (almost) comprehensively test the code. For example, if the unit is a function, students should be given the signature of the function. If the unit is a class, students should be given the UML of the class and the document that describes what each method is supposed to complete.

CODE-BASED:

Students will learn how to create a document containing the set of test cases that (almost) comprehensively covers all the paths in the code. For this assignment, no detailed specification is required, instead a very brief description of the unit is given. However, the code should be available to the students. The output of this project is a document that contains the set of test cases in addition to explanation of how much of the code is covered with this set of test cases. They are required to work with a software such as JCoCo (if the code is in java), to show the test coverage metric for the set of test cases that they have designed. The expectation from the industry partner is to provide the input (i.e., short description and the code) to this project.