Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Write tests to ensure we call to bugsnag on all types of errors #4

Open
sudara opened this issue Aug 31, 2018 · 1 comment
Open

Write tests to ensure we call to bugsnag on all types of errors #4

sudara opened this issue Aug 31, 2018 · 1 comment

Comments

@sudara
Copy link
Member

sudara commented Aug 31, 2018

PerfCheckCI needs tests to ensure state / log is captured to bugsnag when:

* App raises a 500 error
* App raises a 404 error
* App doesn't boot because of 500
* App doesn't boot because of Migrations (this needs to explicitly flag)
* App doesn't exist (config is wrong)
* Arguments given are wrong and Perf Check chokes
* PerfCheck raises 500 somewhere
* PerfCheck times out with Net Http
* PerfCheckCI errors in run_benchmarks!
@Manfred
Copy link
Collaborator

Manfred commented Aug 21, 2019

Is this about reporting errors about PerfCheckCI or the target application?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sudara @Manfred