Captain v1.11.4

This release corrects the usage of and respects some of the CAPTAIN prefixed environment variables when using captain run.

What's Changed

• Respect CAPTAIN_{BUILD_URL,TITLE,COMMIT_MESSAGE} variables in run by @ayazhafiz in #58

New Contributors

• @ayazhafiz made their first contribution in #58

Full Changelog: v1...v1.11.4

Captain v1.11.3

This release fixes a bug with xUnit retries where we were not sufficiently escaping special characters that are meaningful to xUnit. Thanks @jcdickinson for your report, fix, and first contribution!

What's Changed

• update nix by @michaelglass in #56
• fix: escape the .net filter subsitution for shells by @jcdickinson, @michaelglass in #57

Full Changelog: v1.11.2...v1.11.3

Captain v1.11.2

This release adds more data to the JUnit output formatter and provides more diagnostics for understanding if you have misconfigured Captain.

What's Changed

• Protect against misconfiguration by @pierrebeaucamp in #51
• Adds file and line to the JUnit output by @TAGraves in #52

Full Changelog: v1.11.1...v1.11.2

Captain v1.11.1

This release fixes a bug related to the interplay between configuration preventing the ability to run run partition-enabled suites without partitioning.

What's Changed

• Ensure ability to run w/out partition when partition configured by @tonywok in #49

Full Changelog: v1.11.0...v1.11.1

Captain v1.11.0

Improve DX of captain partition functionality by inferring CI provider parallelism and exposing new configuration to partition w/in captain run.

What's Changed

• Push partition command into run w/ partition config by @tonywok in #43
• add back shell escaping to captain run with partitioning by @michaelglass in #44
• merge partitionNodes from generic provider into other providers by @michaelglass in #45
• Prefer generic provider partition settings over unset detected provider by @tonywok in #46
• Fix the hidden (not public) captain parse results command by @kylekthompson in #47
• Fix the assignment of the --framework and --language CLI flags by @kylekthompson in #48

Full Changelog: v1.10.3...v1.11.0

Captain v1.10.3

This release improves the getting started experience for Captain by requiring less configuration.

Changelog

Changed

• captain run no longer requires --who, --branch, and --sha when running in OSS mode.
• --index and --total are now inferred by captain partition for Buildkite, CircleCI, and Gitlab users.

Fixed

• Captain binaries are now signed for macOS.

Captain v1.10.2

This release addresses a handful of formatting issues and bugs using the github-step-summary and markdown reporters.

Changelog

Fixed

• Quarantined and canceled tests now are placed in the correct section of the markdown summary
• Messages and backtraces in the markdown summary are combined in a single <pre> to better handle multiline messages
• ANSI escape codes are stripped from messages and backtraces in the markdown summary
• The github-step-summary no-ops outside of GitHub instead of reporting an error

Captain v1.10.1

This release fixes bugs related to the interplay between command-line flags and the config file.

Changelog

Fixed

• When fixing the interaction between the config file and flags while specifying reporters in #16, a subtle bug was introduced which caused an error when specifying reporters via CLI flag and none via config file.

Captain v1.10.0

This release adds better support for parsing JUnit files. It also adds new reporter options to produce markdown summaries of your test results.

Changelog

Added

• Parser support for JUnit files without a top-level <testsuites> element.
  • In cases where there isn't a top-level <testsuites> element, a top-level <testsuite> element is expected.
• Additional reporter options:
  • markdown-summary: Produces a summary of your results in Markdown.
  • github-step-summary: Writes the output of the markdown-summary to the $GITHUB_STEP_SUMMARY in GitHub Actions.

Fixed

• Previously, the test-suites.*.output.reporters option in the config file was being unintentionally ignored. Now, it is respected and any additional --reporter flags passed to the CLI will be merged with the options in the config file

Captain v1.9.11

Captain is now open source! We built Captain to solve problems around flaky tests and inefficiencies around parallel execution of tests. Captain is a CLI that can detect and quarantine flaky tests, automatically retry failed tests, partition files for parallel execution, and more. It’s compatible with 15 testing frameworks. Captain supports 15 test frameworks with more on the way.

With Captain OSS, you can manage your test suite within your codebase by checking in files containing information about test timings, quarantined tests, and more. And with the paid Captain Cloud offering from RWX, you can automatically track all of this information without needing to check in files in addition to supercharging the OSS feature set with an interactive web interface for managing your test suites.

Get started with Captain at rwx.com/captain.

Changelog

Added

• Ability to explicitly disable Cloud mode through the config file.
• Additional warning messages if Captain is misconfigured.
• A fallback to the pull-request name / number if Captain can't determine a commit message in GitHub Actions.
• Ability to manually set a "title" for a test-suite execution in Captain via CAPTAIN_TITLE or --title. This can be useful if Captain is unable to derive commit messages from your environment.
• Additional options to configure the partitioning delimiter (can now be set via CAPTAIN_DELIMITER)
• Support for passing the suite-id as an argument to captain add and captain remove. Previously this only worked with the --suite-id flag.

Changed

• Some error messages were modified to be easier to understand.