Testing Expected, Boundary and Invalid input
In order to pass this assessment you need to show evidence of testing and debugging for expected input.
For Merit you need to show examples of testing and debugging boundary inputs.
For Excellence you need to show examples of testing and debugging invalid inputs.
For Merit you need to show examples of testing and debugging boundary inputs.
For Excellence you need to show examples of testing and debugging invalid inputs.
Terms
Imagine your pirate boss was asking you how many pieces of Gold you stole. If you stole above 10 then he would congratulate you.
Expected input: Any input that is expected to be entered
Boundary Input
In the case of this program, Our boundary is 10-11 gold pieces. If they answer 10 it is on one side of the boundary. If they answer 11 it is on the other side.
Invalid Input
Testing for invalid input could be but is not limited to 3 different types of responses: Blank, data mismatch and out of bounds data.
Blank --> No response.
Data Mismatch -- > Entering a word rather then a number.
Out of bounds --> Entering a negative number or a number that is way too high.
Blank --> No response.
Data Mismatch -- > Entering a word rather then a number.
Out of bounds --> Entering a negative number or a number that is way too high.
Activity
|
Download and extract the file to the right.
|
| ||
1.) Download the file above, extract it open it in Visual Code
2.) Open the One Note "Programming Testing" document
3.) Enter the values into the program in each testing log with what the expected output should be
4.) Debug the problems that arise.
Please Note: I have given you the values, and you need to show yourself fixing the issue. For every test that fails you will need to do another test to fix the issue.
2.) Open the One Note "Programming Testing" document
3.) Enter the values into the program in each testing log with what the expected output should be
4.) Debug the problems that arise.
Please Note: I have given you the values, and you need to show yourself fixing the issue. For every test that fails you will need to do another test to fix the issue.
Code Commenting - Describing Purpose
For the criteria for the assessment you will need to code comment according to the following criteria:
Achieved: documenting the program with comments.
Merit: Testing and debugging the program to ensure it works on expected and boundary cases.
Activity: Classify the code
The file commenting.html has 3 snippets of code.
In your one note classify them as either "not achieved", "achieved" or "Merit"
Explain why.
Achieved: documenting the program with comments.
Merit: Testing and debugging the program to ensure it works on expected and boundary cases.
Activity: Classify the code
The file commenting.html has 3 snippets of code.
In your one note classify them as either "not achieved", "achieved" or "Merit"
Explain why.
