DEFINITION The criteria that a system or component must satisfy in order to be IEEE accepted by a user, customer, or other authorized entity Formal testing conducted to determine whether or not a system IEEE Acceptance Testing satisfies its acceptance criteria and to enable the customer to determine whether or not to accept the system. This phrase of testing is performed by the final users of the system to provide assurance that the system is ready for production use and can Kaner Acceptance Testing easily be used. This is often called Usability Testing and may also involve ease-of-use validation of user manuals or other documentation. (SEE STABILITY ASSESSMENT TESTING). This phase of testing is performed by the final users of the system to Testing provide assurance the system is ready for production use. This is Acceptance Testing Glossary often called usability and may also involve ease of use of documentation or user manuals. This phase of testing is performed by the final users of the system to Testing provide assurance the system is ready for production use and can Acceptance Testing Glossary easily be used. This is often called usability and may also involve ease of use of documentation or user manuals An evaluation process performed by the recipient of a delivered product usually to validate its readiness for use in a production QA TeamAcceptance Testing environment and to ensure that it satisfies required system and/or business requirements. Used to verify that data requirements (represented in the form of an entity-relationship diagram) support the data demands of process CSTE B Access Modeling requirements (represented in data flow diagrams and process specifications). Company The description of an individual step within the manual test Action Forms procedure. QA TeamAction User input applied to the user interface. A Documented suggestion for change to a process or process-related item that will prevent the future occurrence of defects identified as a IEEE Action Proposal result of defect prevention activities. (See also software process improvement proposal.)

A custom control that takes advantage of Object Linking and Rational ActiveX Embedding (OLE) technology. An ActiveX can be used and tested by SQU Robot in both 16-bit and 32-bit versions of an application A group process that takes large amounts of language data, such as a CSTE A Affinity Diagram list developed by brainstorming, and divides it into categories. A test station that runs a GUI user or multiple virtual users. The Rational Agent test station Agent test station uses SQA Agent software to play back test entries specified in an SQA LoadTest test schedule. A single software product that may or may not fully support a CSTE A Application business function. Application-underRational The software application currently being tested test Company The name of the tester who has been assigned to create or perform a Assigned To Forms test. An independent examination of a work product or set of work IEEE Audit products to assess compliance with specifications, standards, contractual agreements, or other criteria. This is an inspection/assessment activity that verifies compliance with plans, policies, and procedures, and ensures that resources are CSTE A Audit conserved. Audit is a staff function; it serves as the "eyes and ears" of management When the test regeneration compiler is run, it creates a manual test best script file (suffix.TXT) and an automated test script file Automated practice (suffix.REC). The automated script output file is used as an input file to an automated software testing tool. Automated test scripts are produced by an automated softwarebest Automated Test testing tool and are used to test an application in an automated practice Scripts fashion. These automated test scripts are used to test an application in a consistent, repeatable and measurable way. Background Testing a process in a multi-processing system to see how well it Rational Testing does many tasks at the same time. Work waiting to be done; for IT this includes new systems to be developed and enhancements to existing systems. To be included in CSTE A Backlog the development backlog, the work must have been cost-justified and approved for development The actions and test cases (or master data_ captured while recording Rational Baseline a test procedure that establishes the expected behavior of the application-under-test. A specification or product that has been formally reviewed and agreed upon, that thereafter serves as the basis for further IEEE Baseline development, and that can be changed only through formal change control procedures. A group of expected results previously captured to be used to QA TeamBaseline compare current expected results, which will then reveal differences, changes, errors or incompatibilities. QA TeamBaseline A group of expected results captured from the last production release


Kaner IEEE Rational CSTE A CSTE A


Kaner Kaner


Rational Kaner Kaner

of an application. The Baseline is used to verify expected or reveal unexpected differences in the version-under-test. Baseline A quantitative measure of the current level of performance. In configuration management, the application of technical and Baseline administrative direction to designate the documents and changes to Management those documents that formally identified and establish baselines at specific times during the life cycle of a configuration item. Deliberately introducing bugs into a program to see how many the testes find then using this to determine what the possible total BE-bugging number of existing bugs in the whole program may be. (SEE DEBUGGING) A standard against which measurements or comparisons can be Benchmark made. Establishing a base line test to be used as a standard against which Benchmark Testing you can compare performance tests of future versions of the application. (SEE PERFORMANCE TESTING) Comparing your company's products, services, or processes against Benchmarking best practices, or competitive practices, to help define superior performance of a product, service, or support process. A test or analysis conducted after an application is moved into Benefits production to determine whether it is likely to meet the originating Realization Test business case. Testing done by the user rather than by a test group. The users are normally a group of people who are represent the market where the Beta Testing application will be used and use it in the same way(s) that they would if they bought the finished version. Beta testers then give their comments on the application. (SEE USABILITY TESTING) The whole application is tested as one big test (SEE Big Bang Testing INCREMENTAL TESTING) Testing where the program is treated as a black box. The tester can’t Black Box Testing see into the code. The tester feeds in input data, observes output data, and gets results, but does not know how the program woks. A test technique that focuses on testing the functionality of the program, component, or application against its specifications without Black-box Testing knowledge of how the system is constructed; usually data or business process driven. A control through which you access data in a database. If you Bound control change data in a bound control, those changes can be automatically written to the database as you move to another record. All members of a class of test cases cause the program to behave in Boundary between essentially the same way. Anything that makes the program change test classes its behavior marks the boundary between two classes. Testing the program’s response to all extreme input values. Testing Boundary Testing above the upper limits and below the lower limits.



CSTE A Kaner CSTE A Kaner Rational



CSTE A Kaner Kaner Testing

A data selection technique in which test data is chosen from the "boundaries" of the input or output domain classes, data structures, Boundary Value and procedure parameters. Choices often include the actual minimum Analysis and maximum boundary values, the maximum value plus or minus one, and the minimum value plus or minus one. A process for selecting test cases/data by identifying the boundaries that separate valid and invalid conditions. Tests are constructed to Boundary-Value test the inside and outside edges of these boundaries, in addition to Analysis the actual boundary points. Experience suggests that these tests have a higher payoff than valid and invalid values chosen at random. Brainstorming A group process for generating creative and diverse ideas. At a branching point, a program does one thing if a condition is true, and something else if the condition is false. To test a branch, the Branch Coverage tester must test once when the condition is true and once when it is testing criterion false. Complete branch coverage criterion requires testing of all lines and all branches. Also called Complete Coverage of Code. A test method that requires that each possible branch on each Branch Testing decision point be executed at least once. A routine in the application that, when executed, creates an error Bug condition or causes the application to waste unnecessary time. Bug A catchall term for all software defects or errors. Repairs made to an error condition and the supporting documentation Bug Fix to support it. A revision of a software application that corrects defects in or adds Build new features to the previous revision. A description of the stages through which software organizations evolve as they define, implement, measure, control, and improve Capability Maturitytheir software processes. This model provides a guide for selecting Model (CMM) process improvement strategies by facilitating the determination of current process capabilities and the identification of the issues most critical to software quality and process improvement. Casual Analysis The analysis of defects to determine their underlying root cause. A tool used to derive test cases from specifications. A graph which relates causes (or input conditions) to effects is generated. The Cause-Effect information in the graph is converted into a decision table where the Graphing columns are the cause-effect combinations. Unique rows represent test cases. Acceptance of software by an authorized agent after the software has Certification been validated by the agent or after its validity has been demonstrated to the agent. Testing done by an independent or third party test agency to certify Certification that the application does what the specification and requirements Testing documents were designed to have it do. Recording and control of changes made to code or requirements. Change Control Normally managed by a Configuration Management person. Change Control Any changes to the requirements or software must be managed and

Glossary Testing Glossary CSTE B



CSTE B CSTE A Kaner CSTE A Rational


best practice CSTE A

CSTE B Kaner Kaner

can be tracked From the same methods and systems established for tracking problems or defects. Any changes to the requirements or software must be managed and Change Control can be tracked with the same methods and systems established for tracking problems or defects. Change Control Tools that are used to keep track of changes made to systems and all Management Tools related artifacts. These are also known as version control tools. A series of probing questions about the completeness and attributes of an application system. Well-constructed checklists cause Checklists evaluation of areas, which are prone to problems. it both limits the scope of the test and directs the tester to the areas in which there is a high probability of a problem. A formal review of key project deliverables. One checkpoint is defined for each key project deliverable, and verification and Checkpoint validation must be done for each of these deliverables that is produced. Held at predefined points in the development process to evaluate whether certain quality factors (critical success factors) are being Checkpoint Reviewadequately addressed in the system being built. The reviews are conducted by independent experts for the purpose of identifying problems as early as possible. Checksheet A form used to record data as it is gathered. Class of Test Cases Two or more tests that produce the same results. The customer that pays for the product received and receives the Client benefit from the use of the product. An architecture for cooperative processing in which one processor (the client) with primary responsibility for running an application Client/Server requests services or information from a different processor (the server). An architecture for cooperative processing in which one processor (the client) with primary responsibility for running an application Client/Server requests services or information from a different processor (the server). Cloning means to copy a working test script, template or test segment, give it a new name and then make modifications to the new Cloning copy so that it becomes a different test script, template or test segment. Providing advice and encouragement to an individual or individuals Coaching to promote a desired behavior. One version of source or object code is compared to a second version. The objective is to identify those portions of computer Code Comparison programs that have been changed. The technique is used to identify those segments of an application program that have been altered as a result of a program change. Coding Error Errors in the application code that case an error condition. Combinatorial Calculating the number of possible test cases

analysis A centrally located directory structure, typically residing on a network server, containing files used by multiple test stations. If a Common SQA team of testers is recording test procedures, the common SQA directory directory can be used to store header files and user-defined library files. In SQA LoadTest, the common WQQA directory also contains SQA Agent software. A centrally located directory structure, typically residing on a network server, containing files used by multiple test stations. If a Common SQA team of testers is recording test procedures, the common SQA directory directory can be used to store header files and user-defined library files. In SQA LoadTest, the common WQQA directory also contains SQA Agent software. A common test template is a test template that uses data variables to generate different test scripts from the same test template. The data Common Test variables are passed to the test template at compile time. These Template common test templates are used to load an application with transactions or stage test data for other test scripts. It is also a method for reducing the number of test templates to maintain. Checks to see if one part of the application works with another. Compatibility These tests are especially important if the parts of the application testing share the same database. (SEE CONVERSION PROGRAM) A text file that is used as a control file for regenerating any number of manual and automated test scripts. Each compile command listed Compile.CMP File in the Compile.CMP file invokes a test template and associated parameters to create unique test scripts. Compiler Compiler commands are found in the Compile.CMP file. The Command syntax is as follows: #COMPILE filename, template TO output \parm\..parm\ #COMPILE The compile instruction filename A file containing test templates. Template The name of a test template used to regenerate a test script. TO A compile instruction separator. Output The name of the output file for the automated test script. Also the name for the manual test script with a .TXT extension. Parm Variable data that is passed to the test template. Example: #Compile Scenario.TST, FALCON to XYZ.REC \ABC\123\ Remarks: In the example above the two output files would be: 1) XYZ.REC - Automated test script file 2) XYZ.TXT - Manual test script documentation These compiler commands are used to invoke test regeneration using



best practice

Kaner best practice best practice

a test template.

Most compilers for programming languages include diagnostics that identify potential program structure flaws. Many of these diagnostics are warning messages requiring the programmer to conduct Compiler-Based additional investigation to determine whether or not the problem is CSTE B Analysis real. Problems may include syntax problems, command violations, or variable/data reference problems. These diagnostic messages are a useful means of detecting program problems, and should be used by the programmer. A test set containing data that causes each element of pre-specified CSTE A Complete Test Set set of Boolean conditions to be true. In addition, each element of the test set causes at least one condition to be true. Company Complete/TPR Status of a Test Procedure step. Forms The property that all necessary parts of an entity are included. Often, CSTE A Completeness a product is said to be complete if it has met all requirements. Completeness (SEE COVERAGE CRITERIA and BRANCH COVERAGE Kaner Criteria TESTING CRITERION) Based upon applying mathematical graph theory to programs and preliminary design language specification (PDLs) to determine a Complexity-Based unit's complexity. This analysis can be used to measure and control CSTE B Analysis complexity when maintainability is a desired attribute. it can also be used to estimate test effort required and identify paths that must be tested. A parse program looking for violations of company standards. Compliance CSTE B Statements that contain violations are flagged. Company standards Checkers are rules that can be added, changed, and deleted as needed. A white-box testing technique that measures the number of -or percentage - of decision outcomes covered by the test cases designed. Condition CSTE A 100% Condition coverage would indicate that every possible Coverage outcome of each decision had been executed at least once during testing.

Kaner IEEE

Conditional coverage testing criterion Configuration

Checks each of the ways that the condition can be made true or false.





Testing Glossary Kaner CSTE A IEEE CSTE A CSTE A CSTE B

In configuration management, the functional and physical characteristics of hardware or software as set forth in technical documentation or achieved in a product. An element of configuration management, consisting of the Configuration evaluation, coordination, approval or disapproval, and Control implementation of changes to configuration items after formal establishment of their configuration identification. An element of configuration management, consisting of selecting the Configuration configuration items for a system and recording their functional and Identification physical characteristics in technical documentation An aggregation of hardware, software, or both, that is designed for Configuration Item configuration management and treated as a single entity in the configuration management process. A discipline applying technical and administrative direction and surveillance to identify and document the functional and physical Configuration characteristics of a configuration item, control changes to those Management characteristics, record and report change processing and implementation status, and verify compliance with specified requirements. Control of program code and test scripts to insure that the corrected Configuration or modified version of the software is tested with the appropriate Management version of the test scripts. System configuration management is the process of tracking Configuration development software versions or incremental integration builds Management following unit testing and is essential throughout system (system) development. The same methods can be used for managing object and source code libraries and works well for test plan versions. Configuration Tests of different hardware combinations that may or may not be Testing compatible with the program. Testing of an application on all supported hardware and software Configuration platforms. This may include various combinations of hardware types, Testing configuration settings, and software versions. The degree of uniformity, standardization, and freedom from Consistency contradiction among the documents or parts of system or component. The property of logical coherence among constituent parts. Consistency Consistency can also be expressed as adherence to a give set of rules. Consistent A set of Boolean conditions such that complete test sets for the Condition Set conditions uncover the same errors. Control Flow Based upon graphical representation of the program process. In Analysis control flow analysis, the program graph has nodes, which represent a statement or segment possibly ending in an unresolved branch. The graph illustrates the flow of program control from one segment to another as illustrated through branches. The objective of control flow

analysis is to determine potential problems in logic branches that might result in a loop condition or improper processing. If one part of the process is not compatible With another part and they share a common database, a conversion program can rewrite the files in the format needed by the second part of the program. Validates the effectiveness of data conversion processes, including CSTE A Conversion Testing field-to-field mapping, and data translation. The extent to which software is free from design and coding defects CSTE A Correctness (i.e., fault-free). It is also the extent to which software meets its specified requirements and user objectives. Money spent above and beyond expected production costs (labor, Cost of Quality materials, equipment) to ensure that the product the customer CSTE A (COQ) receives is a quality (defect free) product. The Cost of Quality includes prevention, appraisal, and correction or repair costs. 100% coverage occurs when every system and business requirement Testing Coverage is tested by at least one test case or justification given for those not Glossary (Requirements) tested. Specifies a class of program paths that a tester should use because an absolutely complete path testing is normally impossible. Defines Kaner Coverage Criteria achievable amounts of testing that can be done. Also called Logic Coverage Criteria and Completeness Criteria A metric showing the logic covered during a test session, providing insight to the extent of testing. The simplest coverage metric would be the number of statements executed during the test compared to the number of statements in the program. To completely test the prog. Coverage-Based structure, the test data chosen should execute all paths. This is not CSTE B Analysis generally possible outside of unit test, so general metrics have been developed which give a measure of the quality of test data based on the proximity to this ideal coverage. The metrics should consider the existence of infeasible paths (paths designed so that no data will cause the execution of those paths). The parameters of the computing resources deemed to be a source of Critical Computer risk to the project because the potential need for those resources may IEEE Resource exceed the amount that is available. Examples include target computer memory and host computer disk space. A series of dependent tasks for a project that must be completed as IEEE Critical Path planned to keep the entire project on schedule. The individual or organization, internal or external to the producing CSTE A Customer: organization that receives the product. The accounting of repetitions of the execution of any given test case. Company Cycle Normally a number sequence is used that has meaning connected Forms either to the date of the cycle run or other meaningful nomenclature. Cyclomatic CSTE A The number of decision statements plus one. Complexity Conversion Rational Program

Provides the capability to create test data to test validation for the defined data elements. The test data generated is based upon the CSTE B Data Dictionary attributes defined for each data element. The test data will check both the normal variables for each data element as well as abnormal or error conditions for each data element. best Text files that hold input data for a given test script. They are used to Data Files practice load an application with transactions or for staging data in a database. One of a set of predefined tests to be used with the Object Data Test Rational Data Test case to capture the data of an object. (SEE INTERNAL DATA TEST) (SEE DATA TEST) Any data value used in a test template or test segment. A data best Data Variables variable is the name of or reference to a data value. They are used in practice passing data values to test scripts through parameters or data files. Company This is a reference by directory name or document name as to where Dataflow Link Forms further documentation detail for this test case can be found. A source of data that virtual users and GUI users can draw from to Rational Datapool send unique data to the ser4ver. DD (decision-to- A path of logical code sequence that begins at a decision statement or CSTE A decision) path an entry and ends at a decision statement or an exit. Kaner Debugging Finding errors in the program code. (SEE BEBUGGING) The process of analyzing and correcting syntactic, logic, and other CSTE A Debugging: errors identified during testing.. A white-box testing technique that measures the number of - or percentage - of decision directions executed by the test case designed. 100% Decision coverage would indicate that all decision CSTE A Decision Coverage directions had been executed at least once during testing. Alliteratively, each logical path through the program can be tested. Often, paths through the program are grouped into a finite set of classes, and one path from each class is tested. A tool for documenting the unique combinations of conditions and CSTE B Decision Table associated results in order to derive unique test cases for validation testing. Decision/Condition A white-box testing technique that executes possible combinations of CSTE A Coverage condition outcomes in each decision. An unexpected event that occurs while testing or using the application-under-test. A defect may be a bug, a request for an Rational Defect enhancement or new functionality, or any issue requiring corrective action. (SEE BUG) A flaw in a system or system component that causes the system or IEEE Defect component to fail to perform its required function. A defect, if encountered during execution, may cause a failure of the system CSTE A Defect Operationally, it is useful to work with two definitions of a defect: 1) From the producer's viewpoint: a product requirement that has not been met or a product attribute possessed by a product or a function performed by a product that is not in the statement of requirements that define the product; or 2) From the customer's viewpoint anything

that causes customer dissatisfaction, whether in the statement of requirements or not. Rational Defect Tracking CSTE B Defect Tracking Tools A management process that maintains the progress of a defect from opening to closure. Tools for documenting defects as they are found during testing and for tracking their status through to resolution. Text describing the actions to be taken in the test case to achieve an expected objective.

Company Description Forms Design Kaner Document(s) Kaner CSTE A CSTE A Kaner Design Error




CSTE A CSTE A best practice

Parts of the application that fail to execute the expected results as outlined in the Test Requirement Document. The design decomposition of the software item (e.g., system, Design Level subsystem, program, or module). A verification technique conducted by the author of the artifact to Desk Check verify the completeness of their own work. This technique does not involve anyone else. Means that someone reads the program code carefully and analyses Desk Checking its behavior without running test cases at the computer. The most traditional means for analyzing a system or a program. Desk checking is conducted by the developer of a system or program. The process involves reviewing the complete product to ensure that it Desk Checking is structurally sound and that the standards and requirements have been met. This tool can also be used on artifacts created during analysis and design. A group of people working together in business software development. Members of this group could include: project Development Team manager, designers, product manager, technical support, writers and testers A method for running large numbers of test procedures automatically. Distributed With SQA LoadTest, you can perform distributed regression testing regression testing by adding test procedures to a test schedule and running them over multiple test stations. A series of reviews required by Department of Defense directives. Reviews for systems requirements, systems design, preliminary DoD Development design, critical design, functional configuration, physical Reviews configuration, and formal qualification constitute the set of required life cycle reviews. Driver Code that sets up an environment and calls a module for test. Test segments that are exact duplicates of each other. The function Duplicate Test for both test segments is the same even though they have a different Segments name. Lower maintenance occurs when identifying and eliminating duplication test segments.







Kaner CSTE A

Test segments that are exact duplicates of each other. The function Duplicate Test for both test segments is the same even though they have a different Segments name. Lower maintenance occurs when identifying and eliminating duplication test segments. Analysis performed by executing the program code. Dynamic analysis executes or simulates a development phase product, and it Dynamic Analysis detects errors by analyzing the response of a product to sets of input data. A dynamic analysis technique that inserts into the program code Dynamic Assertion assertions about the relationship between program variables. The truth of the assertions is determined as the program executes. Testing is done by executing the code. Black Box and Glass Box Dynamic Testing testing are both dynamic testing types. (SEE STATIC TESTING) Giving people the knowledge, skills, and authority to act within their Empowerment area of expertise to do the work and also improve the process. The individual or group who will use the system for its intended End User operational use when it is deployed in its environment. Required conditions and standards for work product quality that must Entrance Criteria be present or met for entry into the next stage of the software development process. A group of tests forms an equivalence class if they all test the same thing, if they will all likely find the same bugs and if one test will not find a bug it is likely none of them will. Also the tests are in the same Equivalence equivalence class if the tests involve the same input variables, they Classes result in similar operations in the program, they affect the same output variables and non of them force the program to do error handling or all of them do. A test technique that utilizes a subset of data that is representative of a larger class. This is done in place of undertaking exhaustive testing of each value of the larger class of data. For example, a business rule Equivalence that indicates that a program should edit salaries within a given range Partitioning ($10,000 - $15,000) might have 3 equivalence classes to test: - Less than $10,000 (invalid) - Between $10,000 and $15,000 (valid) Greater than $15,000 (invalid) The input domain of a system is partitioned into classes of Equivalence representative values so that the number of test cases can be limited Partitioning to one-per-class, which represents the minimum number of test cases that must be executed. If you expect the same result from two different tests they are considered to be equivalent. An example of an equivalence test Equivalence would be a test that the expected results are Y or N. The Y and y are Testing one equivalence test and the N, n and all other results that are not N or n are equivalent to N or n test. Error Guessing Test data selection technique for picking values that seem likely to cause defects. This technique is based upon the theory that test cases and test data can be developed based on the intuition and experience

of the tester. Some people have a natural intuition for test data or test case generation. While this ability cannot be completely described nor formalized, people's ability to create test data that has a high probability to catch errors should not be overlooked. Guessing carries no guarantee for success, but neither does it carry any penalty. 1. A discrepancy between a computed, observed, or measured value or condition and the true, specified, or theoretically correct value or condition. 2. Human action that results in software containing a fault (e.g., omission or misinterpretation of user requirements in a software specification, incorrect translation, or omission of a requirement in the design specification). An evaluation process performed to validate the error handling code in an application.

CSTE B Error Guessing

CSTE A Error or Defect

Error Recovery Testing Error Recovery Rational Tests the error handling code in an application Tests Execution coverageCalculate how many paths must be tested to meet the completeness Kaner monitors criterion and count how many of these have been tested. Executing the program through all possible combinations of values CSTE A Exhaustive Testing for program variables. Standards for work product quality which block the promotion of CSTE A Exit Criteria incomplete or defective work products to subsequent stages of the software development process. Company The final results that should be produced when the manual test case Expected Result Forms is executed. QA TeamExpected Results A valid outcome of an action or actions within a Test Step. Testing to find expected logical errors but not testing the whole Kaner Exploratory Tests application. External Kaner (SEE FUNCTION TESTING) Specification Taking test scripts that are exactly the same, except for the variable best data, and reducing them to a single test script with a link to a data file Extracting Data practice containing the variable data. This is a method for reducing the number of test templates and test segments to maintain. Useful in identifying regression errors. A snapshot of the correct CSTE B File Comparison expected results must be saved so it can be used for later comparison. The classification of different files and how the files are used. The user determines the suffix. In this document, the following extensions are used: best .TST contain test templates. File Type practice .DAT contain data variables .MAP contain logical test segments .SSP contain test segments with automated script lines. .CMP lists test templates to compile into test scripts CSTE A Flowchart A diagram that shows the sequential steps of a process or workflow. QA Team

CSTE B Flowchart

Rational Focus CSTE A Force Field Analysis

CSTE A Formal Analysis IEEE Kaner Function Function Testing

Pictorial representations of data flow and computer logic. It is frequently easier to understand and assess the structure and logic of an application system by developing a flow chart than to attempt to understand narrative descriptions or verbal explanations. The flowcharts for systems are normally developed manually, while flowcharts of programs can be produced. The state of readiness to receive user input. An object (or control) that has focus indicates this state With a blinking cursor, a highlight color, or some other form of visual feedback. A group technique used to identify both driving and restraining forces that influence a current situation. Technique that uses rigorous mathematical techniques to analyze the algorithms of a solution for numerical properties, efficiency, and correctness. A set of related actions, undertaken by individuals or tools that are specifically assigned or fitted for their roles, to accomplish a set purpose or end. A type of Black Box Testing where functions are tested by feeding them input and examining the output. Internal program structure is not considered. A text file that is used to store test segments. These test segments contain logical groupings of test documentation and pointers to Script.SSP test segments. The function of these test segments are:

best • Navigation through the application Function.MAP File practice • Test functions used by more than one script • One-of-a-kind tests. The compiler uses the Function.MAP file during the regeneration of test scripts. Documentation that describes in detail manual test scripts. This documentation is updated whenever automated script lines are updated. Documentation that describes in detail manual test scripts.

best Functional practice Documentation Kaner Functional Documentation

An evaluation process performed to validate the physical operation QA TeamFunctional Testing of the software by feeding input and examining output. Internal program structure is not considered. Application of test data derived from the specified functional CSTE A Functional Testing requirements without regard to the final program structure. Glass Box (or Testing where the programmers use their understanding and access to Kaner White Box) Code the source code to develop test cases. Testing General Protection Fault. A terminal condition in the Windows Rational GPF application that has violated memory protection rules and caused the application to stop functioning.

Rational GUI Testing GUI Glossary Testing GUI Glossary

Graphical User Interface. The Graphical User Interface is the window screen interface the user sees and works With. The Graphical User Interface is the window screen interface the user sees and works with. A type of test procedure used to play back recorded test cases and GUI actions (such as keystrokes and mouse clicks). Typical users of Rational GUI procedure GUI procedures include regression testing and, With SQA LoadTest, measurement of client response time under multi-user load conditions. A GUI procedure running on an Agent test station. Only one GUI Rational GUI user user at a time can run on a test station. A strategy used to project test more likely to find errors made in the first place, more likely to expose errors so they are more obvious if Kaner Heuristics they’re made, or more likely to detect them errors that will be made, because every program path can not be tested A boundary condition that isn’t apparent to the user, but would be Kaner Hidden boundary apparent to someone reading the code. An object that is not visible through the user interface. Includes nonvisible objects (Visible property is False) and non-visual objects (no Rational Hidden object GUI component). During object selection, use the F4 key to display a list of hidden objects on the Windows desktop. A graphical description of individual measured values in a data set that is organized according to the frequency or relative frequency of CSTE A Histogram occurrence. A histogram illustrates the shape of the distribution of individual values in a data set along with information regarding the average and variation. A computer used to develop software. (See Target Computer for IEEE Host Computer contrast). Incremental Each piece is first tested separately. Also called module testing, unit Kaner Testing Strategy testing or element testing. A set of test scripts that run independent of other test scripts or set of best Independent Test test scripts. Running an independent test script has no impact on practice Scripts other test scripts. The concept of independent testing is that testing is conducted by Testing Independent personnel who have not been involved From theprogramming of the Glossary Testing software being tested to allow more objective testing. The concept of independent testing is that testing is conducted by Testing Independent personnel who have not been involved with the programming of the Glossary TGesting software being tested to allow more objective testing. Independent A buzzphrase referring to verification and validation testing done by Verification and Kaner an independent test agency. (SEE VERIFICATION TESTING) (SEE Validation Testing VALIDATION TESTING) (IV&V) CSTE A Infeasible Path A sequence of program statements that can never be executed. QA TeamInitial Condition The status of the hardware, software, and data that is required prior to

executing a test case. This may include the execution of one or more other test cases. Company Conditions that must be met before a manual test case can be Initial Conditions Forms executed. Anything needing to be done before the test case can be run. (NOTE: QA TeamInitial Conditions this may be running other test cases in a required sequence). Materials, services, or information needed from suppliers to make a CSTE A Inputs process work, or build a product. A formal assessment of a work product conducted by one or more qualified independent reviewers to detect defects, violations of development standards, and other problems. Inspections involve CSTE A Inspection authors only when specific questions concerning deliverables exist. An inspection identifies defects, but does not attempt to correct them. Authors take corrective actions and arrange follow-up reviews as needed. Formalized reviews that use people other than the producer to evaluate the correctness of a single product/deliverable. The product is checked against predetermined entrance criteria or the CSTE B Inspection specifications that were used to build the product. The process requires advanced review of the input specification and the product by competent peers who have been assembled to form an inspection team. The number of virtual users running a single virtual user procedure Rational Instances on a given test station. The insertion of additional code into a program to collect information CSTE A Instrumentation about program behavior during program execution. Incorporates testing into the operational environment. A repository for test information must be pre-established so that the test data can Integrated Test CSTE B be separated from production data. Once established, the integrated Facility test facility permits test transactions to be entered with the same ease as required to enter normal production transactions. CompanyIntegration Test ?????? Forms Case CompanyIntegration Test An individual manual test case, which is a part of a three-tier, test Forms Case???? system. Integration testing addresses the interface integrity and reliability of interfaces: Programs, subsystems, external systems. This includes Testing Integration Testing testing logical groupings of previously united tested units to confirm Glossary that they work together properly as a completed system per the design requirements. An evaluation process performed to validate the integrity and QA TeamIntegration Testing reliability of interfaces between two or more systems. CSTE A Integration Testing

Sign up to vote on this title
UsefulNot useful