You need a test library for running request test. It reproduces your production env piece by piece. You can use whatever you want and create a custom template for the CrashBreak test.
We use integration with GitHub, so our library can create a new branch and push the test into it. Just pull it and fix it!
When your fix is ready, just push it to your repository. CI server confirms your fix and can create a pull request from the exception branch if all tests pass.
Ok, sometimes something goes wrong, let's dump the system!
CrashBreak created a branch and put the failing test there.
It's ready to pull!
CI server automatically runs the CrashBreak test on a specific branch.
Now we see that the recreation of the exception was successful.
It’s time for your part of the job!
Fix the exception easily with the failing test. When it passes, make a commit and pull the fix into a branch!
Again, the CI server automatically runs the CrashBreak test on a specific branch.
Now you can check if your fix also works in other environments.
Integration with our web app automatically marks the exception as solved!
Integration with GitHub can remove the test and do a pull request.
Your part of the job is just to review the fix and merge to a master branch!
Now it's working! Nice!
You didn't even need to run the server or a browser. Just focus on programming!
Of course not! If you don't want to use GitHub integration you can generate the failing test by running one simple command with the error id from our system! The CI server is also only an extension, so you can do it all manually, but our goal is to make the programmer's life simpler and for this, integrations can be really helpful.
You can write custom serializers, integrations, dumpers and restorers. For all this, check out our extensions page! We tried to make our libraries easy to adapt or edit and give you the opportunity to do anything that can help you to fix the bug.
Give us a try!
Remember that you can create your account totally for free with the starter plan!