When software breaks, developers lose hours working out which change caused it, and with microservices the error often shows up in a different service from the one that caused it. CRASH//FORENSICS spots the failure by itself, proves exactly which developer's change broke it by re-testing each change one at a time, and gives the developer a tested fix that they only need to approve.
Built With
- css3
- fastapi
- git
- html5
- javascript
- powershell
- pydantic
- pytest
- python
- uvicorn
Log in or sign up for Devpost to join the conversation.