The idea of CrashBreak is to generate a failing test for production errors and reduce your work to just running the test and fixing the exception. The test can also be generated by us on a specific branch, ready to fetch!
You can adapt our system and libraries for your needs. Our goal is to make a fight with exceptions simple like running a unit test. That's why you can send us anything you need to fix the problem as easily as possible.
Integrate CrashBreak with the CI server, your GitHub server, AWS and many more. Our libraries are suited for programmers and can be adapted to do whatever is necessary to overcome the exception.
To reproduce the error on your local computer with a failing test you need to dump the system when the exception occurs. You can use CrashBreak dumpers or write your own to get enough data for restoring your system. Check out our extensions page.
When you have already dumped the system, send all dumper results to CrashBreak. Remember to protect your sensitive data and store it on your own AWS servers. Send us only links or the name of the file. All information you send will be available in a failing request test.
For each dumper there is a restorer that reproduces your system piece by piece using data sent to CrashBreak. After restoring, the library runs a test simulating the request that created the exception on your production server. Use this test to create a fix. Be sure that the problem will not occur again!