Skip to content

Advanced Settings

Advanced Settings let you customize how CaseRunner generates POMs and test cases for your project. You can use a standard framework with optional custom instructions, or upload your own framework code entirely.

Info

Advanced Settings are available for Web and API projects. Mobile projects use standard frameworks only.

Accessing Advanced Settings

  1. Open your project.
  2. Click the Advanced Settings button (gear icon) on the project page.

Framework Modes

Use one of CaseRunner's built-in frameworks. Optionally toggle on Custom Instructions to add rules that guide generation.

  1. Select a framework from the dropdown.
  2. (Optional) Enable the Custom Instructions toggle and enter your rules.
  3. Click Save.

Upload your own test framework code so CaseRunner generates tests matching your existing patterns.

  1. Select Custom Framework mode.
  2. Upload a .zip archive containing your test code.
  3. Select up to 10 representative files from the extracted archive.
  4. Click "Analyse Codebase".
  5. Review the extracted style guide and compatibility result.
  6. Click Save.

Compatibility Check

After analysis, CaseRunner reports how well your uploaded code matches the project type:

Result Meaning
Full Match Your code is fully compatible with the project type.
Partial Match Some patterns apply but the code targets a different testing type. Review the warnings.
No Match The uploaded code does not match the project type. Consider using a standard framework instead.

Tip

Select files that best represent your project's test structure — page objects, test classes, utility helpers. This gives CaseRunner the clearest picture of your patterns.

Custom Instructions

Custom instructions are free-text rules that guide how CaseRunner generates POMs and test cases. They work with both Standard and Custom framework modes.

You can scope instructions using prefixes:

Prefix Applied To
TEST_CASE: Test case generation only
POM: Page Object Model generation only
GENERAL: Both POM and test case generation (default if no prefix)

Example:

TEST_CASE: Always include negative test scenarios for form validation.
POM: Use descriptive method names that include the action and target element.
GENERAL: Follow AAA (Arrange-Act-Assert) pattern in all tests.

Note

Custom instructions have a 5,000 character limit. Be specific — vague instructions like "write good tests" are less effective than concrete rules.

Next Step

Once your settings are configured, proceed to Generate Test Cases.