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 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.
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. You need to provide:
- Title. It's the title of an external reference, just for organizing purposes.
- URL It's the URL that redirects to a more detailed description of the requirement.
Config versions refer to a Property Manager property version. The versions that you can see in the main 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 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 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 suites 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 the 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 suites are test suites within which test cases are executed in the order they are added and cookies and session information are retained for subsequent 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: Create a test suite.
Client profiles are constituents of test cases. 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. By default, the browser type is set to Chrome, and geographical region to US. See also: Create and add test cases.
Conditions are constituents of test cases. 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. See also: Create and add test cases.
This is the list of available condition types together with their descriptions.
|Response code||Verifies the occurrence of a response code.|
|Response header||Verifies the occurrence of a response header.|
|Content Provider Code||Verifies the settings of the Content Provider Code behavior in Property Manager.|
|Cache key query parameters||Verifies the settings of the Cache key query parameters behavior in Property Manager.|
|Caching||Verifies the settings of the Caching behavior in Property Manager.|
|Ignore case in cache key||Verifies the settings of the Ignore case in cache key behavior in Property Manager.|
|Last mile acceleration (Gzip compression)||Verifies the settings of the Last mile acceleration (Gzip compression) behavior in Property Manager.|
|Log request details||Verifies the settings of the Log request details behavior in Property Manager.|
|Origin server - Cache key hostname||Verifies the settings of the Cache key hostname behavior for the Origin server in Property Manager.|
|Prefetch objects||Verifies the settings of the Prefetching behavior in Property Manager.|
|Redirect||Verifies the settings of the Redirect behavior in Property Manager.|
|SureRoute||Verifies the settings of the SureRoute behavior in Property Manager.|
|SiteShield||Verifies the Site Shield settings.|
|Tiered distribution||Verifies the settings of the Tiered distribution behavior in Property Manager.|
|Variable||Verifies the settings of the Set variable behavior in Property Manager.|
|Alerted rules||Verifies whether an alerted rule in the security configuration is applied to the test request.|
|Denied rule||Verifies whether a denied rule in the security configuration is applied to the test request.|
|Policy name||Verifies whether a policy in the security configuration is applied to the test request.|
|API ID||Verifies whether API registered in API definitions with specific API ID is applied to the test request.|
Test requests are constituents of test cases. They are combinations of:
- Keywords. Keywords are 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 main list.
- URL. A fully qualified URL of the resource to test.
- Additional settings. Additional settings provide details on set of request headers for Test Center to use during a test run.
See also: Create and add test cases.
Variables allow you to reuse specific values in a test request's URL and condition. They enable you to create test cases with complex metadata and run very specific tests.
Each variable consists of a name and an assigned value. You can add and edit variables as well as delete those created by users of your account. You can also view all test cases in which each variable is used. See also: Create and manage variables and Create and add test cases.
Rules is the name of one of the reference tabs in the Tools section of the Create and add test cases window. For test suites associated to a config version, the Rules tab contains the JSON representation of the entire property version’s rule tree. You can use it either as a reference for creating conditions or as a conditions' generator.
When you're creating a new condition or editing an existing one, Test Center highlights all behaviors set for your property in Property Manager. When you double click the highlighted area, Test Center autogenerates a condition for a test case to use.
For test suites not associated to a config version, you can use this tab to associate them.
Hostnames is the name of one of the reference tabs in the Tools section of the Create and add test cases window. If your test suite is associated to a config version, the Hostnames tab contains the list of all the hostnames assigned to a property in Property Manager. You can use it as a reference when creating a test request or to add test cases variations.
See also: Create and add test cases.
Updated 15 days ago