IEEE 829 Standard Test Log Template

-
Test Log Identifier
Some type of unique company generated number to identify this test log, its level and the level of software that it is related to. Preferably the test log level will be the same as the related test case or procedure level. Ideally the test log naming convention should follow the same general rules as the testware it is related to. This is to assist in coordinating software and testware versions within configuration management.
       ·  Unique "short" name for the log
       ·  Version date and version number of log

Description
·  Items being tested and any supporting reference materials
       ·  Case Specification
       ·  Procedure specification
       ·  Transmittal report
·  Date & time
·  Executed by
       ·  Tester
       ·  Observer
·  Environment
        ·  Especially any variances from the planned test environment

Activity and Event Entries
·  Date/time
      ·  Beginning of each significant activity
      ·  End of each activity
·  Execution description
      ·  Procedure executed (reference to its location)
      ·  Personnel present at test
            ·  Tester, developer, observer
            ·  Reason for each persons presence
·  Procedure results
       ·  For each execution, log all relevant information
            ·  Error messages, aborts, interventions
            ·  Location of outputs
       ·  Result status (success, failure, unknown)
·  Environmental information
      ·  Any changes or substitutions from requested environment
·  Anomalous Events
      ·  Record events before and after an anomaly
     ·  Any special situations
          ·  Power interruptions, etc.
·  Incident reports
      ·  Report on each unexpected result or variance from expected output

Comments

Post a Comment

Popular posts from this blog

Types of Review

-
A single document may be the subject of more than one review. If more than one type of review is used, the  order may vary.  It is  apparent that none of the following types of review is the 'winner', but the different types serve different purposes at different stages in the life cycle of a document. The main review types:  Walkthrough Technical Review Inspection Walkthrough A walkthrough is characterized by the author of the document under review guiding the participants through  the document and his or her thought processes , to achieve a common understanding and to gather feedback. This is especially useful if people from outside the software discipline are present, who are not used to, or  cannot easily understand software development documents.  The content of the document is explained step by  step by the author, to reach consensus on changes or to gather information.  Within a walkthrough the author does most of the preparation. The participa
Read more

Roles and Resposibilities for a Formal Review

-
The participants in any type of formal review should have adequate knowledge of the review process. The  best, and most efficient, review situation occurs when the participants gain some kind of advantage for their  own work during reviewing.  In the case of an inspection or technical review, participants should have been  properly trained as both types of review have proven to be far less success-ful without trained participants.  This indeed is perceived as being a critical success factor. The best formal reviews come from well-organized teams, guided by trained moderators (or review  leaders). Within a review team, four types of participants can be distinguished:  moderator author scribe reviewer the management (in addition to the main four roles) The moderator The moderator (or review leader) leads the review process .  He or she determines, in co-operation with the a uthor, the type of review, approach and the composition of the review team.  The mo
Read more

Phases of Formal Review

-
Phases of a formal review In contrast to informal reviews, formal reviews follow a formal process.  A typical formal review process consists of six main steps: Planning Kick-off Preparation Review meeting Rework Follow-up Planning The review process for a particular review  begins with a 'request for review'   by the author to the moderator (or inspection leader).  A moderator is often assigned to take care of the scheduling (dates, time, place and invitation) of the review. On a project level, the project planning needs to allow time for review and rework activities , thus providing engineers with time to thoroughly participate in reviews. For more formal reviews ,e.g. inspections, the moderator always performs an entry check and defines at this stage formal exit criteria. The entry check is carried out to ensure that the reviewers' time is not wasted on a document that is not ready for review.  A document containing too
Read more