captain merge
Merge the test result files produced by partitioned executions into a single set of results.
When you split a test suite across parallel jobs, each job writes its own result file.
captain merge combines those per-partition files and renders reporters (such as markdown-summary) from the combined results.
Usage
captain merge results-glob [results-globs] [flags]
Examples
Merging per-partition JSON results and rendering a single Markdown summary:
captain merge tmp/results/*.json --reporter markdown-summary=tmp/summary.md
Printing a summary of the merged results to the console:
captain merge tmp/results/*.json --print-summary
Options
--config-file <PATH_TO_CONFIG>
Defaulted. Overrides the location of the Captain CLI config file.
--framework <FRAMEWORK>
Configurable. The framework of the test suite. This is required if --language is set.
You only need to set this to disambiguate result files that Captain cannot otherwise identify; the files from a single partitioned suite normally share one framework, so this can be omitted.
These can be set to anything, but Captain has specific handling for supported frameworks.
--help
Displays more information about a command or subcommand.
--language <LANGUAGE>
Configurable. The programming language of the test suite. This is required if --framework is set.
These can be set to anything, but Captain has specific handling for supported frameworks.
--print-summary
Prints a summary of all merged tests to the console.
--quiet
Disables most default output.
--reporter <TYPE=OUTPUT_PATH>
One or more TYPE=OUTPUT_PATH (e.g. markdown-summary=tmp/summary.md) pairs to enable different reporting options.
Available reporters are rwx-v1-json, junit-xml, markdown-summary, and github-step-summary.