Testing

In the design phase you designed a test plan. In the testing phase you carry out that plan and record the results.

You should keep a changelog as part of your project documentation that records:

  • any bugs or errors found during the test
  • the date on which they were found
  • the change proposed to fix the issue

If an error is encountered, then there are tools that can be used to help locate and fix the problem.

Example of a completed test table

Any test methodology used for testing your system should be done in a comprehensive and systematic manner.

Comprehensive

All parts of the system (everything) are tested. Checking that normal, extreme and exceptional data can be handled by the system.

Systematic

The testing is done in a logical order according to a plan.


Types of Error

Logic Error

The code runs, but the outcome does not achieve what was expected. For example, using a > instead of >= in an if statement.

Syntax Error

The code is unlikely to run due to a typo or incorrect syntax. For example, missing the colon at the end of an if statement.

Execution Error

The program crashes during use. This can happen when you try to access a list item that doesn’t exist or divide by 0.

Report a Glow concern
Cookie policy  Privacy policy

Glow Blogs uses cookies to enhance your experience on our service. By using this service or closing this message you consent to our use of those cookies. Please read our Cookie Policy.