Skip to content

CSV Variable Conflicts

CSV Variable Conflicts

OctoPerf automatically detects conflicts when multiple CSV variables interact in ways that could cause unpredictable behavior during test execution. This guide explains what these conflicts are, why they matter, and how to fix them.

When OctoPerf finds a conflict, you'll see an error or warning message at the top of your CSV variable editor.

Info

Conflict detection runs when you open a CSV variable, save it, or when OctoPerf performs a Virtual User sanity check.

  • Errors are blocking: tests cannot run until resolved
  • Warnings are non-blocking: tests can run, but we recommend fixing them to ensure consistent behavior

Conflict Types

Column Name Conflict

What it is: Two or more CSV variables define columns with the same name (ERROR).

Example:

Imagine you have two CSV variables:

  • Variable A: columns username, password, email
  • Variable B: columns username, phone, address

Both use username: this is a conflict.

Why it matters: If your test script accidentally refers to the wrong variable, it will retrieve data from an unintended source. This causes test failures or incorrect behavior that's difficult to debug.

How to fix:

  1. Best option: Rename one of the conflicting column names to make it unique
  2. Rename in the CSV file and update references in your test script

  3. Example: Rename one username column to account_name or user_id

  4. Alternative: If the columns serve different purposes, consider combining the variables if possible

When you fix the CSV file, OctoPerf will automatically detect the resolution after you save.

File Conflict

What it is: Two or more CSV variables reference the same CSV file (WARNING).

Example:

  • Variable A: Uses file credentials.csv
  • Variable B: Uses file credentials.csv

Both pull data from the same file.

Why it matters: This can lead to unpredictable behavior:

  • If you modify the file, both variables see the change unpredictably
  • Virtual users may read different rows than intended
  • Data can become misaligned across your test

How to fix:

  1. Best option: Create separate CSV files for each variable
  2. Copy credentials.csv to credentials_a.csv and credentials_b.csv

  3. Update each variable to reference its own file

  4. Alternative: If both variables legitimately need the same data, consolidate them into a single variable and reference it in both places

When you update the file references, OctoPerf will automatically detect the resolution after you save.

Viewing Conflicting Variables

When OctoPerf detects a conflict, the message shows:

  • What the conflict is (which column name or file is involved)
  • Which other variables are involved in the conflict (with clickable links)

You can click on the conflicting variable names to navigate directly to them for editing.

When Conflicts Are Detected

OctoPerf checks for conflicts when you:

  • Open a CSV variable for editing
  • Save a CSV variable after making changes
  • Run a Virtual User sanity check (before running a test)

If you see a conflict message, address it before running tests to ensure consistent, predictable behavior.

Differences from Content Validation

CSV conflicts are different from CSV content validation errors:

  • Content Validation checks the format of your CSV file (encoding, structure, security issues)
  • Conflict Detection checks relationships between multiple CSV variables

You may see both types of messages. Fix any that appear for best results.

FAQ

Q: Can I have the same column name in different CSV variables?

A: Not without fixing the conflict. If your test script references ${variable.column_name}, OctoPerf needs each column name to be unique across variables to prevent ambiguity.

Q: Is a file conflict always a problem?

A: It depends on your use case. If intentional (multiple variables reading the same lookup data), it may be fine. However, if accidental, it can cause unpredictable behavior. Review and address file conflicts to be safe.

Q: I fixed the conflict — why does it still show?

A: Conflicts re-check when you save. Make sure you:

  1. Updated the CSV file (renamed the column or file reference)
  2. Saved your changes
  3. Closed and re-opened the CSV variable, or clicked away and back to refresh