Overview:
This document describes the GemStar GUI, failure verification process for GemStar test failures, the sources of information, tools, and necessary additional information for proper validation of test failures whether caused by test software, test scripts, operator error, tester hardware problems, or failures of the disc drive units under test.
It begins with an overview of the GemStar GUI, showing most menu functions & sub-GUIs needed for the variety of tasks users may need to perform.
It then goes into detail on the Failure Verification process itself, starting with the outlining of information needed when you need to provide details on a single test failure vs multiple related failures. In either case, sources of information are similar, and these are listed. The result of every failure verification is one of several outcomes, which require various actions.
GemStar Test Results logfiles are examined generally, showing the format of each drive/test’s file, and typical areas of interest for failed tests. Locations of the results logfiles are indicated, along with procedures for finding logfiles for certain drives or groups of drives.
Critical information needed for each test failure is identified, and general guidelines for determining level one cause are listed for each common GemStar failure code (pointers to error-code specific documents may be used as they change more frequently than the general process of verifying failures).
Additional tools and information are documented, and links to other documents are given, for further examination of failures where more effort is needed for determining cause of failure. This can include examination of the drive and it’s self diagnostic abilities, searching for potential bugs in test scripts & software, or performing tasks for conclusively isolating the cause for failure when the culprit is elusive or infrequent.
Overview:
This document describes the GemStar GUI, failure verification process for GemStar test failures, the sources of information, tools, and necessary additional information for proper validation of test failures whether caused by test software, test scripts, operator error, tester hardware problems, or failures of the disc drive units under test.
It begins with an overview of the GemStar GUI, showing most menu functions & sub-GUIs needed for the variety of tasks users may need to perform.
It then goes into detail on the Failure Verification process itself, starting with the outlining of information needed when you need to provide details on a single test failure vs multiple related failures. In either case, sources of information are similar, and these are listed. The result of every failure verification is one of several outcomes, which require various actions.
GemStar Test Results logfiles are examined generally, showing the format of each drive/test’s file, and typical areas of interest for failed tests. Locations of the results logfiles are indicated, along with procedures for finding logfiles for certain drives or groups of drives.
Critical information needed for each test failure is identified, and general guidelines for determining level one cause are listed for each common GemStar failure code (pointers to error-code specific documents may be used as they change more frequently than the general process of verifying failures).
Additional tools and information are documented, and links to other documents are given, for further examination of failures where more effort is needed for determining cause of failure. This can include examination of the drive and it’s self diagnostic abilities, searching for potential bugs in test scripts & software, or performing tasks for conclusively isolating the cause for failure when the culprit is elusive or infrequent.
การแปล กรุณารอสักครู่..