Testing as you work and a test plan.

Testing as you work

While you are creating the product you must test your code as you create it. In fact every time you click "Run" you are conducting a test.

All of your testing must be recorded in a table.

Test number Test description Expected outcome of the test Actual outcome of the test The changes to be made (if necessary)


Include as much detail and evidence as possible in your testing. For best results crop any images outside the table and use cut and paste to move them or use screen clipping.

Test plans

Testing as you work and a test plan.

Writing a test plan

Section 4 begin with the idea of a test plan. You need to write one. These sites will help.

How to Create a Test Plan

Test plan sample: Software testing and Quality assurance Templates

Test Plan (a Real Sample)

Top 10 Attributes Every Sample Test Plan Document Must Have

This is not meant to be a long document, about half a side or so would be sufficient. Use the detail from the websites above to help flesh out your plan. You can base your plan on this example if you wish.

  1. Analyse the product
    1. How can you test a product without any information about it? The answer is Impossible. You must learn a product thoroughly before testing it. You should research clients and the end users to know their needs and expectations from the application
      • Who will use the product?
      • What is it used for?
      • How will it work? (briefly)
      • What is the software/ hardware the product uses?
  2. Design the Test Strategy
    1. What sort of testing are you going to do and when?
      1. Unit testing - specific functions
      2. Integration testing - how functions work together
      3. System testing - testing the complete system as a user would use it.
      4. Install/Uninstall testing - this is self evidence and may or may not be required.
    • What are the risks associated with testing - inexperienced users, tight deadlines.
    • Who will run the testing?
    • When will the testing take place?
  3. Define Test Criteria
    1. Suspension criteria - what would cause you to terminate a test?
  4. Define the Test Objectives
    1. List all of the program features that you want to test - refer to the mind-map at the start.
    2. What are the exit criteria - how will you know that a test is successful? Estimate what proportion of your code is successful.
  5. Resource Planning
    1. The people and technology required for the test to be carried out.
  6. Plan Test Environment
    1. Is the environment a networked desktop or a standalone laptop for example.
  7. Determine Test Deliverables
    1. This plan.
    2. The results of the testing process.


The product under test is Guru99 banking website.

Useful links

Here are links related to programming in Python.


Here are links to a few examples of techniques that may or may not prove useful.

Exemplar material

Here are links to exemplar coursework tasks and their solutions.

Improvement tasks

Here are links to improvement tasks.