!Do not just paste the expected test result as your error.
You could include "expected 'true to be false'", but it should not be the only information provided for a ticket. You should provide as much information as possible on what your code is doing and your interepretation of the instructions / requirements.
- IOCE (if applicable...are you writing a function?)
- What are your inputs? What data type?
- What are your outputs? What data type?
- What are your constraints, if any?
- What are your edge cases, if any?
- In your own words, not code, describe how you are solving the problem.
- In your own words, what do you think is causing the issue?
- Have you done any research?
- If YES, do you have any resource links that you can include? Also provide context for how you got to that resource.
- If NO, google the problem and try to solve on your own for 15 minutes before making a help desk request.
-
Grasp
- Read the entire instructions and fully understand what is required
- Break down the problem into smaller chunks (sub-problems)
- Determine the IOCEs
-
Plan
- Create a plan in english using pseudocode
- For every 1 line of code you should have 1 line of pseudocode
- Indent the pseudocode and avoid using keywords and jargon
-
Code
- Follow your pseudocode accurately
- Test your code as you write it to ensure values are what you expect
- Don't guess, but try things out
-
Debug
- Determine what the problem is by checking the error message(s)
- What line is number is it listed on?
- What does the error mean?
- Have others had this error? Google it.
- Refer to the IOCEs
- Determine what the problem is by checking the error message(s)
