Black-box testingBlack-box testing takes an external perspective of the test object as a basis on which to derive test cases. These tests can be functional or non-functional, though usually functional. The test designer selects valid and invalid inputs and determines the correct output. There is no knowledge of the test object's internal structure. |
White-box testingWhite-box testing (a.k.a. clear-box testing, glass-box testing, transparent-box testing and translucent-box testing or structural testing) uses an internal perspective of the system to design test cases based on internal structure. |
Regression testingRegression testing is any type of software testing which seeks to uncover software regressions. Such regressions occur whenever software functionality that was previously working correctly stops working as intended. Typically, regressions occur as an unintended consequence of program changes. |
Change managementThe Change Management process in Systems Engineering is the process of requesting, determining attainability, planning, implementing and evaluation of changes to a system. It has two main goals: supporting the processing of changes and enabling traceability of changes. See also en.wikipedia.org/wiki/Change_management_(engineering) |
Unit testingUnit testing is a software design and development method where the programmer makes sure that individual units of source code are fit for use. A unit is the smallest testable part of an application. See also en.wikipedia.org/wiki/Unit_testing |
Project/Test projectA Project (also called Test project) is a complete unit that resides completely within one single folder in the file system (all documents and attachments, as well as the database file itself). |
Test unitA Test unit exists in order to group test cases. When operating with a large number of test cases, it is advisable to group test cases together, e.g. place all logically related test cases into one group. Test units can be nested as and where needed and each test unit can contain an unlimited number of test cases. Test units are, if you will, similar to folders inside Windows Explorer which group files (for Zeta Test: test cases) together. |
Test caseA Test case is a specific description of a single test to perform. A test plan usually contains many test cases that are carried out one after each other (or in a random order) by a tester. A test case is always contained within a test unit. Test cases are created “globally”, i.e. all test units created are independent of any specific test plan. You assign test units and test cases when selecting them for a specific test plan. |
Test planA Test plan is a concrete description of test cases to perform, as well as their results. Test plans can be grouped inside test folders, although this is usually unnecessary for small projects, where you can add them directly to the root. |
