Running Pairwise

  1. Open the folder containing Pairwise.

  2. Double click Pairwise jar to run Pairwise UI.

    ui empty
    Figure 1. User Interface
  3. Provide configuration file with data to Pairwise, use the most efficient way for you to do it:

    • drag and drop file into Pairwise area,

      ui drag and drop2
      Figure 2. Provide input file using drag and drop feature.
    • choose file with file explorer […​],

      ui explorer2
      Figure 3. Provide input file using file explorer.
    • Provide file path into text field.

      ui empty2
      Figure 4. Provide input file path into text field.
  4. Choose folder for output file if you want to save it in different location than input file

    • Provide path into text field or choose folder from file explorer:

      ui output folder2
      Figure 5. Provide output file using file explorer.
  5. Choose custom name for result CSV file

    • Provide custom name into test field.

      ui output file2
      Figure 6. Provide custom filename.
  6. Provide additional setup if needed.

    • You may use custom charset, delimiter and additional output file.

      ui preferences2
      Figure 7. Set custom preferences.
  7. Generate test suite.

    • Hit Generate button or use hotkeys.

      ui generate2
      Figure 8. Generate button.
      ui generate3
      Figure 9. Hotkeys.
  8. Check your results!.

    • Check your result file in output folder or directly with link provided by Pairwise.

      to be added
      Figure 10. Output file link.
  9. Check other UI additional features.

Running Pairwise with terminal

Runtime Parameters

There are several parameters which can be passed into AnkrPt Pairwise to control how test generation works. They are:

Parameter Required Example Description




source file for the pairwise criteria



see below

output path or file for the test data to be generated to




overrides the csv delimiter if your default doesn’t work




overrides the csv delimiter if your default isn’t sufficient




generates additional output file, available formats are json and xml.

Using Pairwise to generate XML files if criteria names don’t meet XML specification requirements may be ineffective and end with getting an XML file that is not parsing (criteria names are converted to XML tags).

XML file still will be generated but will need fixes on the user side.


The optional output parameter can define a relative or absolute file or folder. This is how:

  • If output is not included, the output file has "-output" appended to its name before the extension

  • The system determines relative versus absolute (C: is absolute for Windows, for example)

  • If it has an extension (meaning .csv or similar), it is a file and is written directly to that file. If the file already exists, it will be overwritten.

  • If it is not a file, it is a folder.

    • If it is a relative folder, the relative portion is based on your source file, not the executable path.

    • Tests are written with the same filename as the source filename.

  • If the output file already exists, the new filename includes " (copy 999)" before the extension

Outputing a relative folder keeps generated tests together and your source folder clean.

Refer to: running examples.

Custom Delimiters and charset

Using custom DELIMITERS and various CHARSET for CSV files:

  • running Pairwise from terminal with option -delimiter="[delimiter]" (i.e. -delimiter="|") following parameters allows to execute input CSV file with custom delimiter.

  • running Pairwise from terminal with -charset="[charset]" (i.e. -charset="UTF-8") following parameters allows to execute with allowed charset[i.e. UTF-8 or ISO-8859-1].

  • Fill proper fields (Charset/Delimiter) in Pairwise UI

There are some challenges while working with CSV files that are not created with your locale settings. It may be needed to use combination of delimiter & charset setup to run Pairwise correctly.