Skip to main content

Configuration Files

Configuration files define how DevAssure behaves when executing tests.

They contain structured settings (written in YAML) that control:

  • Application details (URL, description, rules)

  • User personas

  • Test data (users, credentials, environment data)

  • Browser & execution preferences

  • Agent instructions

  • CSV column mappings

  • Custom tool definitions

Instead of hardcoding values inside test cases, configuration files centralize project-level behavior inside the .devassure/ folder.

app.yaml​

Describes your application and sets rules the agent follows during execution.

description: >
  About my app
  in multi line
rules:
  - User can't create more than 3 projects
  - Any data deleted can't be restored

personas.yaml​

(Optional) Define user personas referenced in tests.

normal_user:
  description: No admin access, can do all other operations
  age_group: 18-30
  gender: M
  region: USA

admin:
  description: Admin can add or delete other users and manage privileges

deactivated_user:
  description: Login is deactivated by admin

expired_user:
  description: License has expired

test_data.yaml​

Defines URLs, credentials, and test data per environment. The active environment is selected in the Configuration view.

If a key is missing in the selected environment, the default values are used as fallback.

default:
  url: 'http://localhost:3000'
  users:
    default:
      user_name: '[email protected]'
      password: 12345678
    admin:
      user_name: '[email protected]'
      password: 12345678
  stripe_data:
    allowed_card:
      card: 4444 4444 4444 4444
  test_otp: 1122

uat:
  url: 'http://uat.myapp.com'
  users:
    default:
      user_name: '[email protected]'
      password: 12345678
  test_otp: 2345

agent_instructions.yaml​

Runtime instructions that guide agent behavior during test execution — useful for retry logic and fallbacks.

instructions:
  - Reload the app and retry if app shows warning server is busy
  - Sign up a new user and proceed if any of the given logins are not working

preferences.yaml​

Controls browser engine, screen resolution, headless mode, and parallelism.

browsers:
  default:
    browser: chromium
    resolution: 1920 x 1200
    headless: true
workers: 2

csv_mapping.yaml​

Maps your CSV column headers to DevAssure test fields. Required when your CSV uses non-default column names (e.g., exports from TestRail or Jira).

summary: Summary
steps: Steps
priority: Priority
tags: Tags

If csv_mapping.yaml is absent, the agent expects default column names: Summary, Steps, Priority, Tags.

Example — mapping from a Jira export:

summary: Title
steps: "Steps (Expected Result)"
priority: Priority
tags: Labels