Glossary |
![]() ![]() |
Configuration A test configuration is a specific operating system and software setup in which a test case or set of test cases must be run. If a test case is to be carried out on several operating systems, it will contain a separate configuration for each one of those OS’s. Database A database is a collection of custom-built xml files, which describe all details of a test environment. A database can contain many projects, which in turn contain test cases housed in test suites. Generally each software product will have a separate database. Generic Test Case A Generic Test Case is a Test Case, which has not yet been assigned to a project. In this form, the test case does not contain any information relating to the results of the test. In this form, the test case contains the basic test script information required to carry out the test along with some other rudimentary data, such as the create date, required Resources and recommended Configurations. Once a test case is copied or dragged to a project folder, it becomes a Project Test Case. List View The List View is the name given to area on the right hand side of the main TestLog window. It generally displays a list of whatever is contained in the currently selected node of the Tree View. Progress Report A Progress Report is a line chart report. It shows the history of the states of all test cases within a single project. For each day since the beginning of the report, the progress report displays the number of tests in pass, fail and unattempted states. Project A project corresponds logically to a release of a software product. Projects are essentially collections of test cases and reports. A Database may contain many projects, one for each version of the software product, which has been or is being tested. Project Test Case A Project Test Case is a Test Case, which has been assigned to a project. In this form, as well as containing all the information a Generic Test Case contains, it also contains extra data concerned with the execution and results of the test case. This extra data is particularly pertinent for the generation of meaningful Reports. Report Reports are generated on a project basis and display some useful statistics on the test cases within that project. There are two types of report – Progress Reports and Status Reports. Resource A resource is defined as a piece of hardware or equipment required to carry out a certain test case or group of test cases. Status Report A Status Report generates statistics based on the current snapshot of a project. It displays charts, which illustrate the proportions of passed tests to failed tests and the time taken to execute the tests versus the planned time to execute the tests. Test A Test Case contains one or more tests. Sometimes the term Test and Test Case are used interchangeably in this User Guide, but generally Test refers more to the actual steps of the software test, whereas Test Case refers more to the logical representation of the test case including the information concerning results. Test Case A Test Case is essentially a description of a test to be carried out on a software product. Test Cases exist in two basic types – Generic Test Cases and Project Test Cases. Tester A Tester refers to a member of the test team who will actually be carrying out a test or series of tests. Test Suite A Test Suite is a container for Test Cases. Test Suites provide a method of organising your test cases into logical groups. Tree View The Tree View refers to the left pane of the TestLog main window featuring the Windows Explorer style tree structure. You will use this window to do most of your navigation through TestLog. |