Skip to end of metadata
Go to start of metadata

Below is a quick run down on all the major terms and concepts used by Test Management for JIRA:

TERMDESCRIPTION
Test CaseA Test Case is a test artefact developed for a particular test condition, such as to exercise a particular program path or to verify compliance with a specific requirement
Test ScriptA Test Script specifies a sequence of steps and expected results for the execution of a Test Case. Also known as Manual Test Script or Test Procedure Specification
Test CycleA Test Cycle is an ordered list of Test Cases assigned to Testers and Test Environments created to achieve specific testing goals. Also known as Test Run or Test Set
Test ResultA Test Result is generated when a Test Case is executed. It stores the tester responsible for the execution, the execution date, the defects submitted, the environment and the status of the execution (eg: Passed, Failed, etc)
Test EnvironmentA Test Environment is an attribute of a Test Result. It is used to determine the environments to be tested for each Test Case. Planning your Test Environment includes defining your platform coverage, such as: operational systems, browsers, databases, etc


The tight integration between Adaptavist Test Management and JIRA means you can reuse elements created on JIRA and avoid duplication of commons elements such as: Projects, Users, Versions and so on. The following diagram shows a high-level overview of the relationship between Adaptavist Test Management and JIRA:

  • No labels