ConductedTests

ConductedTests is a term used in software testing to denote tests that have been executed and whose results have been recorded. It can refer to a collection of test cases that have been run, a phase in a project’s testing workflow, or a formal artifact within a test-management system.

A ConductedTest typically includes the test case identifier, steps performed, input data, expected results, actual results, pass/fail status, tester identity, environment details, timestamps, and any defects linked to the test outcome. When multiple tests are executed as part of a test run, the run serves as a container for the ConductedTests and provides aggregate metrics such as pass rate, defect density, and coverage. In automation contexts, ConductedTests may be generated as results of an automated test suite, including logs and screenshots; in manual contexts, testers manually record outcomes.

Purpose and use of ConductedTests is to enable traceability from requirements to verification, support defect triage, and enable auditing and quality assessment. It helps distinguish executed work from planned tests that have not yet been run. The ConductedTests artifact supports reproducibility by capturing the environment, data, and steps necessary to validate results and by linking outcomes to corresponding test cases and defects.

Management and storage of ConductedTests typically occur within test-management tools, defect trackers, or versioned repositories. Naming conventions may include software version, testing environment, and date. See also: Test case, Test plan, Test run, Test management, Quality assurance.