Customising Execution with Test Case Level Settings

SimplifyQA offers configuration flexibility at two levels:

• Project Level Settings – Applied globally to all test cases within a project.

• Test Case Level Settings – Applied only to an individual test case, overriding the default project-level configurations for that specific testcase.

This enable users to define custom parameters (e.g., wait times, timeouts, paths) specific to the behavior and needs of a single test case.

Purpose

Test Case Level Settings are particularly useful when:

• A specific test case requires longer wait or timeout durations.

• A test case downloads files to a unique path.

• There is a need to isolate or fine-tune performance for a critical scenario.

Available Attributes

Each setting is defined as a key-value pair.

Attribute	Description	Example Value
MINIMUM_WAIT	Minimum wait time between operations	1000 ms
MEDIUM_WAIT	Medium-level wait time	10000 ms
LONG_WAIT	Long wait time for complex processes	30000 ms
MAX_TIME_OUT	Maximum wait duration for an element or step before failure	90000 ms
IF_TIME_OUT	Wait time for conditional (if-else) checks	5000 ms
EXIST_TIME_OUT	Timeout to wait until an element appears	45000 ms
NOT_EXIST_TIME_OUT	Timeout to wait until an element disappears	5000 ms
DOWNLOAD_PATH	Custom download directory path for that test case	D:/Downloads/TestFiles

Note: All timeout and wait values are in milliseconds. The values override the defaults during test execution.

Max Timeout refers to the maximum duration (in seconds) the system will wait for an element or action to complete during test execution. If the element doesn't appear or the action isn't completed within this time, the step fails. It's useful for handling slow-loading elements or dynamic waits.

How to Configure Test Case Level Settings

1. Open the desired test case.

2. Navigate to the Settings tab.

3. Add or update key-value pairs according to your test’s requirement.

4. Click Save to apply the changes.

You can also add new rows using the + Add Row button and remove any row if no longer needed.

• These settings are applied only when the specific test case runs.

• If a parameter is not defined, it falls back to the Project Level default.

• You can use this feature to experiment with different test environments or performance thresholds without affecting other test cases.

Use Case Example

Suppose you have a test case that downloads a report which takes more time than usual:

• You can increase MAX_TIME_OUT to 120000 ms.

• Set a custom DOWNLOAD_PATH like C:/Reports/Test1.

This ensures the test case runs successfully without unnecessary delay or failure due to timeout.