Artifact: Test Log










var backPath = './../../';
var imgPath = './../../images/';
var nodeInfo=[{view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_mp7z0DIDEdqwaNnSEheSAg", "_1yMJAN7YEdmjRZts2c4ZjQ", "{A719CEAE-35FB-42F6-A076-F501B83E5B85}", "{528F34BA-0118-40F3-8D29-DE60EF4183A6}"]}, {view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_mp7z0DIDEdqwaNnSEheSAg", "_4EQgMDIEEdqwaNnSEheSAg", "_SPvXcN7IEdm8G6yT7-Wdqw", "{528F34BA-0118-40F3-8D29-DE60EF4183A6}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_f6_YwN7DEdmsEI4YDGX2ag", "_1yMJAN7YEdmjRZts2c4ZjQ", "{A719CEAE-35FB-42F6-A076-F501B83E5B85}", "{528F34BA-0118-40F3-8D29-DE60EF4183A6}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_EOvXUN7HEdm8G6yT7-Wdqw", "_SPvXcN7IEdm8G6yT7-Wdqw", "{528F34BA-0118-40F3-8D29-DE60EF4183A6}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_jijhYAIaEdqEutyfYo0quQ", "_qUsPIN7REdmjRZts2c4ZjQ", "{528F34BA-0118-40F3-8D29-DE60EF4183A6}"]}];
contentPage.preload(imgPath, backPath, nodeInfo, '', false, false, false);










Artifact: Test Log















This artifact contains raw output captured during a unique execution of one or more tests.


Domains: Test
Work Product Kinds: Project Data






Purpose



To provide verification that a set of tests was executed, and To provide information relating to the success of those tests.



Relationships



RolesResponsible:



Tester


Modified By:



Implementer


Tester





TasksInput To:



Determine Test Results





Analyze Runtime Behavior


Output From:



Execute Developer Tests


Execute Test Suite





Process Usage


Configuration & Change Management
 > 
Manage Change Requests
 > 
Test Log


Implementation
 > 
Implement Components
 > 
Test Log


Implementation
 > 
Integrate each Subsystem
 > 
Test Log


Test
 > 
Validate Build Stability
 > 
Test Log


Test
 > 
Test and Evaluate
 > 
Test Log


Test
 > 
Achieve Acceptable Mission
 > 
Test Log






Description



Main Description The Test Log provides a detailed, typically time-based record that serves both as verification that a set of tests were executed, and provides information relating to the success of those tests. The focus is typically on the provision of an accurate audit trail, enabling post-execution diagnosis of failures to be undertaken. This raw data will subsequently be analyzed to help determine the results of some aspect of the test effort. A test Log usually representing the output resulting from the execution of a Test Suite for a single test cycle run.


Brief Outline Each Test Log should be made up of a series of entries that present an audit trail for various aspects of the test execution including, but not limited to, the following: the date and time stamp of when the event occurred a description (usually brief) of the event logged some indication of the observed status additional contextual information where relevant additional details relating to any anomalous or erroneous condition detected



Tailoring



Representation Options Automation tools often provide their own Test Log facilities, which can be extended or supplemented with additional logging provided both through custom user-routines and the use of additional tools. The output may take one single or many different forms. Typically, Test Logs have a tabular or spreadsheet-like appearance, with each entry comprising some form of date and time stamp, a description of the event logged, some indication the observed status, and possibly some additional contextual information. If you are using automated test tools, such as those found in the Rational Suite family of products, much of the above functionality is provided by default with the tool. These Test Log facilities typically provide the ability for the capture, filtering and sorting and the analysis of the information contained in the log. This allows the Test Log to be expanded in detail or collapsed to a summary view as required. The tools also offer the ability to customize and retain views of the Test Log for reporting purposes. Where the logic that produces an automated Test Log simply appends new information to an existing log file, it will be necessary to provide sufficient storage to retain the Test Log file. An alternative solution to this approach is to use a ring buffer. A good explanation of using Ring Buffer Logging to help find Bugs is presented in a pattern catalog by Brian Marick. (Get Adobe reader.) This catalog provides an overview of other classic problems with using automated Test Logs.





©  Copyright IBM Corp. 1987, 2006.  All Rights Reserved.







contentPage.onload();