Inspect crashes online as soon as they occur. See how frequent each exception is. Filter out the ones you have already seen.
You install CrashKit client code into your application.
CrashKit client code intercepts unhandled exceptions and sends them to the server.
CrashKit web application processes the exception reports and allows to view them online.
CrashKit automatically gathers product version, os version, processor type and other small yet important details.
Learn about new bugs before your users even notice. Fix them before the users complain.
We won't spam your inbox, though: similar crashes are never reported twice during the day.
Not all crash reports are created equal. Some differ in details. Some have different stack traces, but still occur at the same spot.
1000s of similar exception reports are grouped into 10s of bugs. You only have to see and deal with those bugs.
That's why we can avoid filling up your inbox: you are getting only one e-mail per bug per day.
See the bugs that only happened in your QA environment separately. And also separate are the bugs happening on developer machines.
Expect more QA tools to come as CrashKit evolves.
1. Add CrashKit client code to your project.
2. Tell it your app name and version.
3. Feed all your uncaught exceptions into CrashKit.
Assign ticket ids to CrashKit bugs. Open the assigned ticket in one click. Quick ticket creation coming soon.
Lighthouse, Trac and Redmine are supported.
Currently we support:
Java, including OSGi applications,
Python, including Google App Engine,
PHP,
JavaScript for your AJAX code.
Please tell us what else you need by specifying it when signing up for the beta. We'll do our best. (Or just e-mail your ideas to us.)
We are only running a limited beta at the moment. But we promise to invite you within a month.
