levo
Log inStart

The Development Project: Build, Testing and Evaluation

Carrying out and recording the testing

  • 3 things to know
  • A2 Unit 2

Overview

Running each test against its expected result, capturing evidence, recording a failure with its cause and the change made, re-running the fix and the tests around it, and tracing every requirement to a test.

What you need to know

Answer each one before you reveal it.

Your recallNot started
Key term

How is the test log used after the project is finished?

Key term

How is testing recorded?

Key term

Why is evidence captured for each test?

Questions from this subtopic

Each one with the model answer underneath.

  1. 1

    How is testing recorded?

    Model answer

    Each test in the plan is run in turn and the actual result is written beside the expected one, with evidence such as a screenshot, and a note of what was done where the two differed and when the test was re-run.

  2. 2

    Why is evidence captured for each test?

    Model answer

    Evidence shows the test was actually run and what the system did, so the record can be checked by someone else. A tick against a test proves nothing on its own.

  3. 3

    What should be recorded when a test fails?

    Model answer

    A failure is recorded with the actual result, the diagnosis of the cause, the change made to correct it, and the outcome of re-running the test and of the regression tests around it.

  4. 4

    Why is a failed test valuable rather than a setback?

    Model answer

    A test that fails has done its job: it has found a fault before a user did. A test run that finds nothing at all is more likely to mean the tests are too gentle than that the system is perfect.

  5. 5

    What is a test log?

    Model answer

    A test log is the completed record of every test run, in order, with its result and any follow-up, which together form the evidence that the system was tested as planned.

  6. 6

    Why must a test that failed and was fixed be re-run and the re-run recorded?

    Model answer

    A recorded fix is not evidence that it worked. Only the re-run shows the fault is gone, and only the record shows the re-run happened.

See the rest and revise

Other ways to work this

The same content, four other ways.

What is inside Levo

Six ways to work the same material.

1Closed book
2Open book
3Closed book

The 3-step method, run for you

Answer cold, learn it, then prove it stuck. Levo tracks the jump between your first attempt and your last.

Systems Analysis and Development Approaches
Design, Development and Testing
Implementation and System Security
Programming

Cram a whole paper in one sitting

Sort every topic into what you know and what you do not, then drill only the weak ones.

A check requires a value.
presencerangeformat

Blank Blitz makes facts automatic

Rapid timed gap-fills on the terms and numbers you need to recall without thinking.

ANormal data is 12, which should be accepted.
BBoundary data is 1 and 50, which should be accepted.
C0 and 51, just outside the limits, should be rejected.

Build It gets the exam shape right

Assemble a full-mark answer from its marking points, in the order an examiner wants them.

One byte is made up of 8 bits.
TrueFalse

Test It catches misconceptions

Spot the fault in a statement. The traps are the mistakes students actually make.

721941163128510

Brain Breaks between sessions

Short focus games to reset attention, so the next set lands better than the last.

Every question in The Development Project: Build, Testing and Evaluation, on a schedule.

Attempt a question from memory, write the correct version, then attempt it again. Levo records the jump between your first attempt and your last, and brings each question back on the day you are due to forget it.

Start revising, £5 a monthSee how the method works

Or £46 a year, about £3.83 a month. Cancel anytime.