All Projects → bahmutov → send-test-info

bahmutov / send-test-info

Licence: other
Attach unit test information to exceptions sent by Raven to Sentry

Programming Languages

javascript
184084 projects - #8 most used programming language
HTML
75241 projects

Projects that are alternatives of or similar to send-test-info

zend-sentry
A Zend Framework 3 module that lets you log to the Sentry.io service.
Stars: ✭ 34 (+100%)
Mutual labels:  sentry, raven
good-sentry
Sentry broadcasting for good process monitor
Stars: ✭ 15 (-11.76%)
Mutual labels:  sentry, raven
aiohttp-sentry
An aiohttp server middleware for reporting failed requests to Sentry
Stars: ✭ 35 (+105.88%)
Mutual labels:  sentry, raven
redux-sentry
Middleware that logs all your store and actions on exception to Sentry with raven-js
Stars: ✭ 13 (-23.53%)
Mutual labels:  sentry, raven
raven-python-lambda
Sentry/Raven SDK Integration For AWS Lambda (python) and Serverless
Stars: ✭ 48 (+182.35%)
Mutual labels:  sentry, raven
sanic-sentry
Sentry integration to sanic web server
Stars: ✭ 31 (+82.35%)
Mutual labels:  sentry, raven
sentry-testkit
A Sentry plugin to allow Sentry report interception and further inspection of the data being sent
Stars: ✭ 78 (+358.82%)
Mutual labels:  sentry, raven
Sentry Javascript
Official Sentry SDKs for JavaScript. We're hiring https://grnh.se/ca81c1701us
Stars: ✭ 6,012 (+35264.71%)
Mutual labels:  sentry, raven
raven2
Raven II Surgical Robot
Stars: ✭ 43 (+152.94%)
Mutual labels:  raven
cygger
Boilerplate generator for API Testing from Swagger to Cypress
Stars: ✭ 20 (+17.65%)
Mutual labels:  cypress
serilog-sinks-sentry
A Sentry sink for Serilog
Stars: ✭ 34 (+100%)
Mutual labels:  sentry
react-cypress-demo
Демонстрация работы библиотеки cypress.io
Stars: ✭ 17 (+0%)
Mutual labels:  cypress
amazin
A MERN-stack app for eCommerce platform, Webshop, Web Store. Storybook: https://www.amazin.one/ Alternative: https://ntrix.github.io/amazin-story
Stars: ✭ 27 (+58.82%)
Mutual labels:  cypress
charts
A Kubernetes Helm Chart for Sorry Cypress, an open-source on-premise, self-hosted alternative to cypress dashboard.
Stars: ✭ 26 (+52.94%)
Mutual labels:  cypress
cypress-gh-action-example
Example running Cypress tests inside GitHub Action
Stars: ✭ 29 (+70.59%)
Mutual labels:  cypress
svelte-pwa-now
A PWA ready Svelte v3.0 starter template with Tailwind, Now integration and optional Typescript suppot
Stars: ✭ 138 (+711.76%)
Mutual labels:  cypress
wongames
🎮 Ecommerce de jogos no estilo Steam. Desenvolvido com Next.js, TypeScript, GraphQL, etc.
Stars: ✭ 18 (+5.88%)
Mutual labels:  cypress
scpx-wallet
Scoop Wallet: Core open-source, multi-asset & cross-platform CLI
Stars: ✭ 18 (+5.88%)
Mutual labels:  raven
sentry-ocaml
A work-in-progress OCaml client for Sentry
Stars: ✭ 26 (+52.94%)
Mutual labels:  sentry
FastAPI-template
Feature rich robust FastAPI template.
Stars: ✭ 660 (+3782.35%)
Mutual labels:  sentry

send-test-info

Attach unit test information to exceptions sent by Raven to Sentry

NPM

Build status semantic-release js-standard-style

Read Connecting crash reporting with end to end tests

Install

Add this module to any project that uses Cypress for end to end testing and Raven.js client to send exceptions to Sentry.

npm install --save-dev send-test-info

Use

From any spec file, require and call a single function with the spec's filename.

const sendTestInfo = require('send-test-info')
// filename is optional
sendTestInfo({spec: __filename})

describe('Test page', function () {
  // unit tests
})

See example spec file cypress/integration/send-test-info-spec.js and the test page cypress/index.html

Result

Each exception captured by Raven and sent to Sentry will include the spec filename and the full test title.

images/sending-error.png

Errors generated during end to end tests can be quickly triaged and recreated by just looking at the exception tags

images/sentry-view.png

API options

You can pass multiple options that control how many times it will search for Raven and add context. See cypress/integration/send-test-info-spec.js as an example.

sendTestInfo({
  spec: __filename,     // the name of the spec file
  maxCheckTimes: 10,    // how many times we should try finding Raven
  maxRavenInstalls: 1,  // how many times should we find Raven
                        // and keep looking again. Good if there are new pages
                        // loaded and Raven is installed again
  interval: 1000,       // interval (ms) between checks for Raven
  debug: true,          // print log messages to the console
  immediate: false,     // start searching for Raven immediately without
                        // using "beforeEach" callback. Good for setting up
                        // inside a Cypress command (like "login")
  breadcrumbs: false    // record Cypress commands as breadcrumbs (see below)
})

Cypress breadcrumbs

This module also subscribes to Cypress events using Cypress.on(...) syntax and adds the information to the Raven breadcrumbs. As the result, the exception will have very useful list of logical steps taken by the test before the crash.

Cypress breadcrumbs

Small print

Author: Gleb Bahmutov <[email protected]> © 2016

License: MIT - do anything with the code, but don't blame me if it does not work.

Support: if you find any problems with this module, email / tweet / open issue on Github

MIT License

Copyright (c) 2016 Gleb Bahmutov <[email protected]>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].