Skip to content

Testing

Debugging and Alpha Testing

Test your software solution thoroughly so you can show that it meets requirements as expected.

Carry out debugging and alpha testing throughout development, and document it using testing tables.

Your testing should include:

  • test cases
  • relevant test data

Your testing tables should include:

  • expected results
  • actual results
  • a clear description of the test
  • the test data used

Do not hide failed tests. Record them and explain the actions or fixes taken. That shows how your solution improved through the testing process.

Beta Testing

Design, conduct and document beta tests with two or more potential users of the software solution.

Potential users could include:

  • the actual client
  • students acting as real users of the software solution

Beta testing can be carried out by:

  • observing users interacting with the solution
  • surveying users about their experience

Document the results so you can identify errors and issues.

Recommendations

Use the beta-testing results to make recommendations for improving the appearance and behaviour of the solution.