Software Test Item
(Redirected from Software Test)
Jump to navigation
Jump to search
A Software Test Item is a test item that represents a testable software artifact or software component that undergoes software testing to verify its software quality attributes.
- AKA: Test Object, Software Under Test (SUT), Test Target, Software Testing Artifact.
- Context:
- It can typically serve as Test Subject through software test execution.
- It can typically exhibit Software Behavior through test interaction.
- It can typically contain Software Defects through implementation flaws.
- It can typically demonstrate Software Capability through functional testing.
- It can typically reveal Software Quality through test result analysis.
- ...
- It can often require Test Environment through execution dependency.
- It can often generate Test Output through behavioral response.
- It can often consume Test Input through data processing.
- It can often interact with External Software Components through integration points.
- ...
- It can range from being a Atomic Software Test Item to being a Composite Software Test Item, depending on its software test item granularity.
- It can range from being a Static Software Test Item to being a Dynamic Software Test Item, depending on its software test item execution requirement.
- It can range from being a Isolated Software Test Item to being an Integrated Software Test Item, depending on its software test item dependency level.
- ...
- It can be evaluated by Software Testing Methods for quality assessment.
- It can be documented in Test Specifications for test planning.
- It can be monitored through Test Instrumentation for behavior observation.
- It can be versioned in Configuration Management Systems for change tracking.
- It can be associated with Software Requirements for traceability management.
- ...
- Example(s):
- Code-Level Software Test Items, such as:
- Component-Level Software Test Items, such as:
- System-Level Software Test Items, such as:
- Interface Software Test Items, such as:
- Configuration Software Test Items, such as:
- ...
- Counter-Example(s):
- Test Cases, which are test specifications rather than testable artifacts.
- Test Datasets, which are test inputs rather than test subjects.
- Test Tools, which are testing instruments rather than tested objects.
- Test Reports, which are test outputs rather than test targets.
- Hardware Test Items, which test physical components rather than software artifacts.
- See: Test Item, Software Testing, Software Test, Software Quality Assurance, Test Artifact, Software Component, Software Under Test.
References
2023
- chat
- Q: When someone says they completed a software test, what did they do?
- A: When someone says they completed a software test, it typically means that they have gone through a process of evaluating the functionality, performance, and overall quality of a software product or application. This can involve several different types of testing such as unit testing, integration testing, system testing, acceptance testing, and others. The goal of a software test is to identify and isolate any bugs, glitches, or other issues that may impact the user experience, and to ensure that the software meets specified requirements and specifications. The extent and specifics of what was included in the "software test" that was completed will depend on the context and the nature of the software being tested.