week 4
Documentation:
requirements specification;
internally documented code
Testing and debugging:
test plan structure eg test, date, expected result, actual result, corrective action;
error messages;
PHP error messages can vary
| Notice | This is normally a simple message that reminds users of an oversight this could be the simple use of a variable that has not been declared |
| Strict notice | This is advice from the interpreter that could refer to "deprecated" code, this is code that is not supported as it could be out of date. |
| Warning | An error in the code somewhere that could be happening, however, it is not enough for the interpreter to stop running the PHP scripts. |
| Parse error | This refers to a syntax error or issue that has stopped the interpreter from running the code and outputting the results, this could be a missing semicolon. |
| Fatal error | This is a major problem with the code forcing it to stop from running. |
other eg specialist software debugging tools
Coding Time
Logic
Arrays
How to obtain the screen resolution.
Last Updated
2018-05-22 13:41:32
Links to Learning Outcomes |
Links to Assessment criteria |
|
|---|---|---|
English
Maths
How 2's Coverage
Anonymous Assessment - Learners assess an anonymous piece of work containing deliberate mistakes against given success criteria.
Anonymous Assessment - Learners assess an anonymous piece of work containing deliberate mistakes against given success criteria.
Files that support this week
Week 3←
PrevWeek 4←
PrevWeek 5←
Prev→
Next→
Next
