New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

cypress-testrail

Package Overview
Dependencies
Maintainers
1
Versions
23
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

cypress-testrail - npm Package Versions

23

2.10.0

Diff

Changelog

Source

[2.10.0]

Added

  • Added description to README how to use an Api Key instead of the user password.
  • Added documentation on how to use Cucumber and Gherkin documents with the integration.
  • Added support for process.env variables. All configuration settings will now also consider entries in process.env.
  • Added new option to ignore pending tests. If ignored, these tests will not be sent to TestRail. Please see README for more.
  • Added new created_run.json file that is created in "Create Run Mode". This allows to immediately read and use data of the created run in other steps of your CI pipeline, while Cypress is running.

Fixed

  • Fixed problem with wrong elapsed_time. When skipped tests were detected coming in Cypress v13, it led to a wrong calculation of the elapsed time.
boxblinkracer
published 2.9.0 •

Changelog

Source

[2.9.0]

Changed

  • Use the Cypress test title instead of the plain "Tested by Cypress" in the TestRail comments (thx @vijigit)
  • Updated Axios dependency to version ^1.6.2 (thx @MelaAxel)

Fixed

  • Fixed a broken elapsedTime error with Cypress v13 in combination with undefined values for the duration of tests.
boxblinkracer
published 2.8.2 •

Changelog

Source

[2.8.2]

Fixed

  • Fixed broken screenshots upload in Cypress 13.
boxblinkracer
published 2.8.1 •

Changelog

Source

[2.8.1]

Fixed

  • Fixed broken elapsedTime calculation with Cypress v13.
boxblinkracer
published 2.8.0 •

Changelog

Source

[2.8.0]

Added

  • Skipped tests in Cypress will now be sent as "blocked" to TestRail (only in createTestRun mode).
  • Add option to provide a list of TestRail RunIDs with runIDs. This will send all test results to all provided run IDs.

Fixed

  • Fixed crash with missing browser when running in UI mode with experimentalInteractiveRunEvents turned on.
boxblinkracer
published 2.7.1 •

Changelog

Source

[2.7.1]

Added

  • Added better test case extraction by removing comma character, if accidentally existing (thx @asalgado87)
  • Add new output, if the integration is not correctly configured.
boxblinkracer
published 2.7.0 •

Changelog

Source

[2.7.0]

Added

  • Added new configuration runIncludeAll that automatically adds all test cases to test runs when creating dynamic runs. (thx @williamatpaper)
  • Added new configuration screenshotsAll that sends all screenshots of all attempts of a failed test to TestRail. ( thx @williamatpaper)
  • The integration now also works if you have accidentally provided "http://" and "https://" within your TestRail domain.
boxblinkracer
published 2.6.0 •

Changelog

Source

[2.6.0]

Changed

  • Results are now sent as "batch" request to TestRail at the end of the file. This safes API requests by only sending 1 request for a spec file (excluding screenshot requests).
  • Changed the output color of debug texts to gray.
boxblinkracer
published 2.5.0 •

Changelog

Source

[2.5.0]

Added

  • Added new CLI Setup Wizard to build your configuration in an interactive way. (see README)
  • The integration will now automatically send the screenshots to TestRail for every failed test. This is all automatically done as soon as the new variable is enabled (see README).
  • Added option to provide optional "suiteId" when creating new runs. If you have a project with suites, this parameter is required.

Changed

  • new README with better instructions and overview
boxblinkracer
published 2.4.0 •

Changelog

Source

[2.4.0]

Changed

  • Tests with status "pending" had been sent as "failed" to TestRail. These test results will now be skipped and not sent to TestRail.

Fixed

  • Improved error response handling from TestRail API. Some errors led to an "undefined reading 'status'" exception. There should still be no error, but now we should know better what happens.
SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc