Glossary

A

Admin

See Administrator.

Administrator

User role that has access to all functionalities in Klaros-Testmanagement.

Artifact

An Artifact is a definable object like a Project, Iteration, Requirement, Test Environment, System under Test, Job, Test Case, Test Suite or Test Case.

B

Bugzilla

Bugzilla is an open source bug tracking and testing tool.

C

Category

Artifacts can be assigned to any number of user-defined categories. Using Categories Users can group related Artifacts together.

C

Coverage

A database is a collection of information organized into interrelated tables of data and specifications of data objects.

Compliance

D

Database

A database is a collection of information organized into interrelated tables of data and specifications of data objects.

Defect

See Issue.

Defect Management System

See Issue Management System.

E

E-Mail

Electronic mail, often abbreviated as e-mail, is any method of creating, transmitting, or storing primarily text-based communications with digital communications systems.

Error

An error is the inability of the system to perform a test correctly. Not to be confused with Failure.

F

Failure

A failure is a discrepancy between a computed, observed, or measured value or condition and the true, specified, or theoretically correct value or condition. Not to be confused with Error.

G

Guest

User role that can display artifacts and reports but may not change any data.

GUIdancer

GUIdancer is an Eclipse-based tool for automated functional testing through the Graphical User Interface (GUI).

I

Incident

See Issue.

Incident Management System

See Issue Management System.

Issue

The term issue is a unit of work to accomplish an improvement in a system. An Issue could be a bug, a requested feature, task, missing documentation, and likewise.

Issue Management System

An Issue Management System (Issue Tracking System) is a software to manage Issues.

Issue Tracking System

See Issue Management System.

Iteration

An iteration is a complete development loop resulting in a release (internal or external) of an executable product, a subset of the final product under development, which grows from iteration to iteration to become the final product (ISTQB glossary).

J

Java

Java is a programming language. Most often, Java is used as a abbreviation for Java Runtime Environment, which needs to be installed in order to run Klaros-Testmanagement.

Java Runtime Environment

The Java Runtime environment needs to be installed in order to execute applications programmed in the Java programming language.

JavaScript

JavaScript is a scripting language most often used to add functionality to web pages. Most newer Web browsers can process JavaScript generated code.

Java Runtime Environment

See Java Runtime Environment.

JIRA

JIRA is a bug tracking, Issue tracking, and project management system by Atlassian Software .

Job

Jobs may consist of the execution of Test Cases, Test Suites or any other possible task. Jobs can be nested and assigned to individual users. The executions and results of jobs can be tracked by Klaros-Testmanagement.

Jubula

Jubula provides automated functional GUI testing for various types of applications.

JUnit

JUnit is a unit testing framework for the Java programming language.

M

Manager

User role that has access to create, edit, delete and search for objects, run test cases and test suites, show results and generate reports.

Mantis

Mantis (MantisBT, Mantis Bug Tracker) is an open source bug tracking system.

O

Operating System

An operating system (commonly abbreviated to either OS or O/S) is an interface between hardware and applications. It is responsible for the management and coordination of activities and the sharing of the limited resources of the computer. Common contemporary operating systems include Microsoft Windows, Mac OS, Linux, BSD and Solaris.

OS

See Operating System.

P

Postcondition

Environmental and state conditions that must be fulfilled after the execution of a test or test procedure.

Precondition

Environmental and state conditions that must be fulfilled before the component or system can be executed with a particular test or test procedure.

Project

A project is the main unit that contains all other Artifacts that are needed to execute Test Cases.

Q

QFTest

QF-Test is a professional tool for automated testing of Java and Web applications with a graphical user interface from Quality First Software.

R

Redmine

Redmine is an open source bug tracking, issue tracking, and project management system.

Requirement

A condition or capability needed by a user to solve a problem or achieve an objective that must be met or possessed by a system or system component to satisfy a contract, standard, specification, or other formally imposed document (After IEEE 610).

Role

A role defines the rights the rights a user has regarding the application or selected projects.

In Klaros-Testmanagement a user can take the role of an Administrator, Manager, Tester or Guest.

S

Selenium

Selenium is a web browser automation tool primarily used for automated testing of web apps. Selenium is able to produce JUnit-compatible test results, which can be imported into Klaros-Testmanagement.

SUT

See System under Test.

System Account

A System Account is a user that is not able to login at the login page and interactively control the application. System Accounts may be used for automated tasks like importing test results.

System under Test

A System under Test is used to represent a version of a software product that can be tested.

T

Test Case

A Test Case is a set of input values, execution preconditions, expected results and execution post-conditions, developed for a particular objective or test condition, such as determine whether an application or software system meets its specifications.

Test Case Result

The final verdict on the execution of a test and its outcomes, like pass, fail, or error. The result of error is used for situations where it is not clear whether the problem is in the test object.

Test Case Step

A test case step consists of execution preconditions, expected results and execution post-conditions for a single action during test execution.

Test Environment

Test Environments represent the extrinsic settings that may influence the test result. Examples for components of a Test Environments are the Operating System or an application server (e.g. Tomcat 7 on Ubuntu 12.10).

Tester

User role that has access to display artifacts and reports and run jobs, test cases and test suites.

Test Execution

The process of running a test by the component or system under test, producing actual result(s).

Test Run

The result of running a test case or test suite under the same system under test and test environment giving or more test case result(s).

Test Suite

A test suite is a set of test cases and the test cases can be executed in groups. The test suite will be used to verify and ensure that a product or system meets its design specifications and other requirements.

Trac

Trac is an open source bug tracking and issue tracking system.

U

URL

A Uniform Resource Locator (URL) specifies where an identified resource is available and the mechanism for retrieving it. Examples for URLs are http://www.klaros-testmanagement.com/" or file:///C:/klaros.txt

W

Web browser

A Web browser is a software application which enables a user to display and interact with text, images and other information typically located on a Web page at a Web site on the World Wide Web or a local area network.

Windows

Windows is the name of several Operating Systems by Microsoft.