All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- Removes support for reporting to Blinka, removing the need for httparty.
- Makes
Capybara.save_path
relative to the current working directory for images
- Adds support for
BLINKA_APPEND=true
to append to existing JSON-files.
- Handles empty test results.
0.7.0 - 2022-03-06
- Support multiple
--path
calls to combine results from multiple files. - Replaces
BLINKA_JSON
andBLINKA_APPEND
withBLINKA_PATH
. - Adds all reporter options as CLI-options instead of using environment variables. -
BLINKA_REPOSITORY
=>--repository
0.6.1 - 2022-02-27
- Rspec
- Improve handling of newlines in backtrace
- Adds more testing
- Handles multiple screenshot tags
0.6.0 - 2022-02-20
- Adds support for Rspec.
- Remove support for
BLINKA_REPORT
, instead usebundle exec blinka-reporter --blinka
for reporting. - Remove
BLINKA_TAP
and replace withbundle exec blinka-reporter --tap
. - Restructure gem internals.
- Support Rspec screenshots.
0.5.2 - 2022-02-01
- Require MFA for pushing to Rubygems
0.5.1 - 2022-02-01
- Look for screenshots in
Capybara.save_path
to allow different output folders for screenshots.- For example a Rails application can be configured with
Capybara.save_path = ENV.fetch('CAPYBARA_ARTIFACTS', './tmp/capybara')
which can then be overriden in CI.
- For example a Rails application can be configured with
0.5.0 - 2022-01-21
BLINKA_APPEND
allows multiple test-runs to be appended to the same JSON-file.
0.4.0 - 2021-03-27
- Change tempus of failing results from
failed
tofail
.
0.3.6 - 2021-03-25
- Removes dependency on mimemagic.
- Only allow images of
jpeg
orpng
format, handles their mime-types by extension.
0.3.5 - 2021-03-11
- Move commit and tag to JSON-report instead of setting in the reporting client. This allows the report to be made by a general script instead of in the test environment. In preparation of supporting Github Actions without access to secrets.
0.3.4 - 2021-02-24
- Reported test cases now include the line in the file where they are defined, previously the line number was connected to the backtrace.
0.3.3 - 2021-02-13
- Use
HEROKU_TEST_RUN_COMMIT_VERSION
defined on Heroku CI when reporting test results to Blinka.
0.3.2 - 2021-02-12
- Allow to report with
BLINKA_REPORT
while using in testsWebMock
.
0.3.1 - 2021-02-12
- Setting
BLINKA_REPORT
with credentials allow report to be sent to Blinka directly at the end of the test run.
0.3.0 - 2021-02-08
- BREAKING 🚨 - Require setting environment variable
BLINKA_JSON
to any value to generateblinka_results.json
used for reporting to Blinka.
0.2.1 - 2021-02-08
- Raise error if configuration to report to Blinka is missing when reporting.
0.2.0 - 2021-02-07
- Adds support for reporting test results in TAP-format.
0.1.1 - 2021-02-04
- Correct the homepage on rubygems.
0.1.0 - 2021-02-03
- Support for adding tag to report using
BLINKA_TAG
environment variable.
- No longer support
BLINKA_BRANCH
, useBLINKA_TAG
instead.
0.0.3 - 2021-02-02
- Allow supplying which git commit sha to report.
0.0.2 - 2021-02-01
- Debug print for which commit hash was reported.
0.0.1 - 2021-01-31
- Setup LICENSE and CHANGELOG.
- Handle inconsistency in source_location of test result in Minitest for different versions.