CrashBreak: A new approach for dealing with production exceptions and bugs in Ruby
Hello! Some time ago I was working on an application that had many bugs and reproducing each one was time consuming. I thought about making this process faster and more user-friendly.
Recreating bugs manually in the browser by typing data and setting all connected modules in the same way like when the exception occurred can be annoying. Also, there is no certainty that the bug is reproduced in the same way it occurred. The other problem is that many of the bugs are hard to reproduce and connected to different layers of the system.
The idea of CrashBreak is to reproduce the exception from the staging server on the programmer’s computer by running a request test. In order to do this the library needs to dump your system piece by piece. Currently we have 3 dumpers: for database, all request data (headers, url, body) and user session.
We tried to create the whole system in an adaptive way. It means that you can write your own extensions to adapt the library to your needs.
The beta of the service is ready and available at http://crashbreak.com
Please give it a try and send me your feedback so I can make CrashBreak even better.
Thank you kind strangers!
Michał Janeczek
Comments
1) the link does not work because of the dot at the end 2) wait… what? So it works by dumping all my db end sending it to you? Am I correct?
Hi!
Of course not!
You are able to dump your database and send it wherever you want. To CrashBreak you only need to send a name of specific dump. For example: “Crashbreak - database dump 2015-09-24 (1443034920.1010225)”. Database restorer uses this name to download specific dump file from your storage.
Post a comment