Testing Technology Glossary - A

• Acceptance test. Formal tests conducted to determine whether or not a system satisfies its acceptance criteria and to enable the customer to determine whether or not to accept a system. This particular kind of testing is performed with the STW/Regression suite of tools.
• Action statement. A non-decision statement in a program that results in executable code.
• Activation clause. A clause in the SMARTS' ATS file which is comprised of the activation keyword and a sequence of system commands to be performed during test execution.
• Ada. The DoD standard programming language.
• Ancestor node. A node in a STW/Coverage directed graph that lies on some path (i.e., sequence of logical branches) that leads to the specified node.
• apg. All Paths Generator. A TCAT-PATH facility that generates equivalence classes that include all program paths from a directed graph.
• Arc. In a directed graph, the oriented connection between two nodes. This is also referred to as an edge.
• Archive file. A file generated from STW/Coverage's cover, scover or ctcover utility containing test trace information in reduced form.
• ASCII synchronization. The process by which a playback (e.g. from CAPBAK/X) holds back execution until a character string is located.
• ATS. A SMARTS user-designed description file which references a test suite. Test cases are referenced in a hierarchically organized structure and can be supplemented with activation commands comparison arguments, pass/fail evaluation criteria, and system commands. When SMARTS is run on either a X Window or UNIX system, the ATS is written in SMARTS' Description Language (which is similar to C language syntax). The ATS file is written in SMARTS C-Interpreter Language when SMARTS is run on a MS Windows system.
• AUT. Application-under-test.
• Automated Test Script. See ATS.
• Automatic flow control. When CAPBAK/UNIX is being run in terminal emulation record mode, a record of the manual flow control is stored in the keysave file and response file.When CAPBAK/UNIX is transmitting keys in playback mode the flow control is maintained by using the information saved in these files.
• Automated Test Script. See ATS.
• Automatic flow control. When CAPBAK/UNIX is being run in terminal emulation record mode, a record of the manual flow control is stored in the keysave file and response file.When CAPBAK/UNIX is transmitting keys in playback mode the flow control is maintained by using the information saved in these files.