Every night, Cofactor uses your app the way real people do and reports anything that breaks.
Several agents use your app at the same time, each signed in as a different kind of user. When something breaks, Cofactor checks it again before it files an issue.
Each agent signs in with its own account, so it sees what that user would see.
When an agent finds a page it hasn’t seen before, it comes back to it on the next run.
A failure is run again before it’s reported, so one bad run won’t create an issue.
Cofactor remembers what it has already covered and spends more time on the parts it hasn’t.
Real users abandon checkouts, use discount codes after they expire, and change plans partway through the month.
Users hit the back button, submit forms twice, and open the same record in two tabs. Cofactor tries this too and checks that nothing breaks.
Names with apostrophes, text pasted from Word, and very large exports. Cofactor tries inputs like these on the forms it finds.
Does it run against production?
No. We set up and manage separate environments for you, so fuzzing never touches your production data. You choose when it runs.
Will it create junk data?
Yes, but it doesn’t matter. We manage the environments for you and they’re all disposable, so the data is thrown away after each run. You choose which parts of your app are in scope.
How is this different from a fuzzer?
A traditional fuzzer sends random input to a single function. Cofactor uses your whole product as a signed-in user trying to get things done, and checks whether the results make sense.
Join the waitlist, or book a call and we will map your surfaces.