(IEEE) Documentation specifying inputs, predicted results, and a set of execution conditions for a test item. Syn: test case specification. See: test procedure.
A set of test input execution conditions, and expected results developed for a part icular objective, such as to exercise a part icular program path or to verify compliance with a specific requirement. [D04885] RUP
In order to test the usability of the prototype, test cases (emanating from the scenarios) are written and saved in the Test specification.
Test documentation that specifies inputs, predicted results, and a set of execution conditions for a test item. Also known as a test case specification or a test procedure.
As used in these project, an executable unit of the material in the test suite which implements one or more Test Purposes (hence verifies one or more Test Requirements). Example. An SVG test file which contains an elliptical arc element with a negative radius. In practice in these projects, the relationship of TRs to TCs can be many-to-many.
A test case is equivalent to concrete alternative executions of a BUC specifying alternative mappings from the BUC onto one or more SUCs, describing the alternative preconditions, specifying alternative inputs and the corresponding expected output and post-conditions. MUMMY
A complete and independent specification of the actions required to achieve a specific Test Purpose (or a specified combination of Test Purposes ).It may be a Generic Test Case , Abstract Test Case or Executable Test Case . source: ITU-T X.290 domain: OSI Conformance Testing usage: EU-P201
a testing work product that automatically performs a single test on an executable work product.
A description of a test to be executed, focussed on a specific test aim.
a document that describes an input, action, or event and an expected response, to determine if a feature of an application is working correctly
a noted/documented set of steps/activities that are carried out or executed on the software in order to confirm its functionality/behavior to certain set of inputs
a sequence of inputs that is input to P during one execution
a set of test inputs, execution conditions, and expected results that test for the achievement of a particular system result
a small unit of code that tests a specific scenario
a specification of inputs to and outputs from your function
a specific business scenario)
a specific test intended to verify one particular aspect of a Product/ Component under test
a step by step plan set on a specific area of the game that needs to be tested for stability or functionality or whatever
A specific test to be performed, including the specific steps necessary for completing the test. Test cases typically describe actions or steps and the expected results of the action or step.
A set of input s, execution precondition s, and expected outcomes developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement. After [IEEE,dob
Documentation specifying inputs, predicted results, and a set of execution conditions for a test item. [XQual] A test case is a bunch of steps that lead to consider one "item" as successfully working. [ANSI] A set of test inputs, execution conditions, and expected results developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement [do178b?]. Documentation specifying inputs, predicted results, and a set of execution conditions for a test item. [C&A] A document describing a single test instance in terms of input data, test procedure, test execution environment and expected outcome. Test cases also reference test objectives such as verifying compliance with a particular requirement or execution of a particular program path.
A specific set of test data and associated procedures developed for a particular test.
Test Case is a commonly used term for a specific test. This is usually the smallest unit of testing. A Test Case will consist of information such as requirements testing, test steps, verification steps, prerequisites, outputs, test environment, etc. A set of inputs, execution preconditions, and expected outcomes developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement.