Bugs that know their build
Every bug knows which build found it and which build fixed it. Crashes, testers and players report into the same place, and a person decides what becomes work.
Bugs & QA
What is inside
- The Bugs page Grouped like an error tracker: how often, since which build, for how many players.
- Crashes One bug per crash group from Sentry, Backtrace or BugSplat, or from kumo's own receiver for Unreal's crash reporter, kept current with its count, builds and platforms.
- The in-game reporter Testers report from inside the game, with the build and the screenshot attached, in a Shipping build when the studio turns it on.
- Player feedback Steam reviews and Discord messages proposed as bugs, for a person to confirm, merge or dismiss.
- A public bug form A form anyone can send a bug through.
- Playtests The build to play, who plays it, a survey, and the feedback grouped and turned into tasks.
- Test runs Test suites and their runs against a build.
- Certification Checklists for the platforms' requirements, run against a release build.
In the subscription
In every kumo plan, free for a team of up to five
It comes with the subscription's Planner. Prototype is free for a team of up to five; a bigger team pays per member seat, and readers are free.
In the docs
One app