Skip to content

The Test Log

BEFORE WRITE

Your job in the design documentation is to tell the colleagues who will work with you how the development should take place. With the Test Log, all you have to do is to write about how columns would be added to the Test Plan to allow the tests to be documented.

Let's compare the Plan and the Log

TEST PLAN

Here are the headers used in the supplied template: Test Plan Headers

TEST LOG

Remember, you have not seen the template yet

However, you can say what the additional columns will be used and describe what their usage is as shown in the next section.

You are not entering any actual test log items at this stage.

TEST LOG COLUMNS

Part 2: Test Log Column Usage

Description of test

  • The items are brought forward from the Test Plan (Strategy) document
  • Can be derived from the 'Type of test to be carried out' column

Test data to be used (if required)

  • Some tests need data to be evaluated. Include that here if that is the case.

  • You might get items from the Prerequisites and Dependencies column of the Test Plan

Expected outcome

  • The anticipated result of the test
  • Be as specific as possible whilst remaining brief.

Actual outcome

  • This column would record what the result of the test was
  • If successful, the word 'Success' might do here
  • If failed, more detail would be needed to describe what happened

Comments and intended actions

  • Say 'No further action' if that is the case.
  • Describe what needs to be fixed if that is the case.
  • Define the dependencies of any fixes needed.
  • Optional: give the issue an ID

Common statements that might be used

  • Pass: Actual Result matches Expected Result.
  • Fail: Actual Result does not match Expected Result.
  • Blocked: The test could not be executed due to a blocker (e.g., a critical bug in a prerequisite feature).
  • Skipped/N/A: The test was intentionally not executed (e.g., out of scope for the current sprint).
  • Example: Pass, Fail, Blocked

Bug ID (if applicable)

  • Purpose: If a test case fails, this column links it to a bug report in a bug tracking system.
  • Example: BUG-001, HTML-1234 (if using HTML)

Comments/Notes

  • Purpose: Any additional information, observations, or context relevant to the test execution. This can be very useful for debugging or clarifying the test result.
  • Example: Minor UI glitch observed, Performance was slow during this test, Unable to reproduce bug on subsequent attempts.