Functional testing concepts

Here are all terms you may encounter when working with the functional testing.

The concepts are arranged in the same order as you can see them in the Functional testing tab.

Requirements describe business requirements that drive configuration changes. You can add the full description or add hyperlinks to external references that provide a more detailed description. To run a test for the requirement it must have test suites containing test cases associated. See also: Run a test for a requirement.
External references
Those are references which provide you and other Test Center users more information about a particular requirement. For example a ticket in your ticketing system.
It’s the title of an external reference, just for organizing purposes.
It’s the URL that redirects to a more detailed description of the requirement.
Config version
Config version refers to a Property Manager property version. Those versions that you can see in the master list differ from those in Property Manager because they are saved with data from Test Center, namely associated test suites and test cases. To run a test for the config version you need to associate it with test suites that include test cases. See also:Add and configure config versions, Run a regression test.
Test suites
Test suites act as containers for test cases. You can add a name and description to a test suite to provide more details about the test suite and the included test cases. You can also set if the test suite needs to be locked or stateful. Test suites can be tested as test objects associated to config versions and requirements or on their own. See also: Run a test for test suites, Run a test for a requirement, Run a regression test.
Locked test suite
It's a test suite that can be modified only by its editors and owners. Test Center users who create locked test suites automatically become their owners, but they can also designate other owners. Editors can edit a locked test suite (except for the Locked status), add new test cases to it, and remove those already included. If the test suite is also stateful, editors can reorder included test cases. Owners can additionally manage the test suite's edit access and remove it. Every Test Center user can send a request for edit access to test suite's owners. Owners are notified about the request with an email. Once they approve or reject the request, the user also gets a notification email. See also: Give the edit access to a locked test suite.
Stateful test suite
It’s a test suite within which the test cases are executed in the order they are added and cookies and session information are retained for subsequent test cases.
Test cases
A test case in functional testing is the basic unit of testing. It includes all settings for which the test needs to be run: conditions, test requests, and client profiles. You can combine a few test cases in a test suite or run a test for a single case. See also: Run a test for test cases, Create a test suite, Create test cases.
Client profiles
Client profiles are constituents of test cases (functional). They are combinations of a browser type, a geographical region, and an IP version that characterize what a client uses to make a test request. In the Client profile tab you can only check which test cases use the selected profile, you can’t create a new one. See also: Create test cases.
Conditions are constituents of test cases (functional). They are the criteria to be evaluated on the HTTP response corresponding to the test request or a specific config setting applied to the test request. For example, Response header foo has a value that equals bar or Caching option is no-store. In the Conditions tab you can check which test cases use the selected condition and create a new one. See also: Create test cases.
Test request
Test requests are constituents of test cases (functional). They are combinations of a fully qualified URL and request headers for which you want to run a test. In the Test request tab you can check which test cases use the selected requests or create a new one. See also: Create test cases.
They’re used for filtering test requests. After you create a test request with particular keywords, you can later find it quickly by entering the keywords into the filter field above the master list.
It’s the URL of the resource to test.
Additional settings
Additional settings of test request provide details on set request headers of test requests for Test Center to use during a test run.