Test Settings |
Test Settings lets you to configure the behavior of test framework for manual tests. including parameters for all services, System Variables, Customer Variables, Test Environments and Credentials.
Note |
---|
If you have multiple test profiles, you can create, duplicated, edit and switch active profiles in Profile management. Test Settings reflects always to the current Active Profile. |
This topic contains the following sections:
In this section you can change the configuration of service simulation services, such as adjust the TCP port used to expose simulated services, queue length, maximum connections, etc. for ordinary usage, you don’t need to change these settings. But when performance test is planned, you may need to increase max queue length and thread count to allow more parallel connections.
System variables are variables declared in simulated services, usually they are environment dependent values such as service Host Name, Port, Uri, Path or other tokens. You need to set these variables for each test environment declared.
Custom variables are defined by user and can be used to replace tokens in Requests, Replies and some automated test steps. Values of custom variable are also environment dependent, which means you need to assign a value for each test environment.
Credentials stores the user name password used to authenticate yourself when calling a service. For example, for those service protected by Basic Authentication and Digest Authentication.
If the service uses Windows Integrated Authentication, NTLM or Kerberos, you don’t need to set credentials here, these kind of authentication uses your Windows Identity automatically. Make sure your windows identity have access to the target service.
All test settings will be stored in a Profile, which you can export for another user or embedded in an automated test project.
In test settings, you are able to define one or more test environments. For each test environment, set values for system variables, custom variables and credentials.