Glossary
Note: Many of these definitions are of how Ken TestMan uses the term.
A-E
Access Key When you install Ken TestMan you are asked for an access key. This should be provided when you downloaded/purchased Ken Testman. The AccessKey is tied to your user details and defines which edition you are using.
Admin Administration role. There are 2 types of administrator in Ken TestMan, a Project Admin and an Application Admin.
Application Admin Administration role. Application Admin is the highest level of user rights and allows the user to create new projects and to add/edit and delete users.
Artefact A testing document, such as a test case, a requirement, a defect etc.
Build The name given to a version of the software of a system under test. Test Cases are executed against a 'Build' of software. This allows you to see your test results against the different Builds.
Component A part of the system under test, used within Ken TestMan to organise Requirements and Test Cases.
Component Tree A folder like structure allowing you to organise you Requirements and Test Cases in any hierarchical structure you like.
Configuration file A file on the server that defines a number of settings that control how Ken TestMan behaves.
Edition There are 3 editions of Ken Testman, Free, Standard and Professional. For more information visit the Ken TestMan website.
Environment The hardware and software environment in which you tests are run.
Execution The process of running a Test Case against a System Under Test and recording the result.
K-O
Lock When a user edits an artefact a lock is taken to prevent other users making changes. The duration of the lock is defined by the LOCKTIMEOUT setting in the configuration file. The user will get a warning message once 75% of that time has expired.
Project Administrators can clear a forcably remove alock from an artefact through the Admin menu.
P-T
Project The highest container within Ken TestMan. All test artefacts belong to a Project. Users can be assigned to different projects with different roles on each.
Requirement A characteristic that the system must posess. Requirements are used to define what the system should do and are therefore important documents when establishing the expected outcome of executing a Test Case.
System Under Test The system being tested, often referred to as SUT.
Test Case A document that descibes inputs, a procedure to follow and the expected outcome of following that procedure. Ken TestMan has been created to document, manage and track the execution of Test Cases.
Test Suite A logical group of Test Cases that are to be executed together.
U-Z
XML is a format that allows you to structure and store data. In Ken TestMan XML documents can be sent to the XML Interface and you will get an XML document in response. This allows third part applications to communicate with Ken TestMan.