SE333-433: Class Activity #4 The intention of these class activities are to encourage you to think of testing in a more rigorous way than you may be used to. These exercises also hint at the strong relationship between specification clarity, faults, and test cases. Please submit an image of your notes to d2l under class activity 2 1. Consider a program which reads a date in the format of mm/dd/yyyy and prints out the next date. For example: Input: 01/31/2018 Output: 02/01/2018 Constraint Assumption: The year is between 1800 and 2200 inclusive (a) Write valid equivalence classes for each entry (b) Write invalid equivalence classes for each entry. (c) Write a data point for each of classes above. (d) How many weak normal tests do you have? Write them down. (e) How many strong normal test cases do you have? Try to write a few down. (f) How many weak robustness test cases do you have? Try to write a few down. (g) How many strong robustness test cases do you have? Try to write a few down SE333-433: Class Activity #4 The intention of these class activities are to encourage you to think of testing in a more rigorous way than you may be used to. These exercises also hint at the strong relationship between specification clarity, faults, and test cases. Please submit an image of your notes to d2l under class activity 2 1. Consider a program which reads a date in the format of mm/dd/yyyy and prints out the next date. For example: Input: 01/31/2018 Output: 02/01/2018 Constraint Assumption: The year is between 1800 and 2200 inclusive (a) Write valid equivalence classes for each entry (b) Write invalid equivalence classes for each entry. (c) Write a data point for each of classes above. (d) How many weak normal tests do you have? Write them down. (e) How many strong normal test cases do you have? Try to write a few down. (f) How many weak robustness test cases do you have? Try to write a few down. (g) How many strong robustness test cases do you have? Try to write a few down