Why we are building this
The most argued-about thing in software testing is not the bug. It is whether the test was really run.
Before BountyShift we ran an independent testing service. Every project reached the same scene: the report is delivered, the client gets stuck on one case, and the question "was this actually tried?" lands on the table. We never had anything but a screenshot to answer it with.
Both sides were right. The client could not see that what they paid for had been done, and the tester had no way to show their work except to describe it. Every time, the argument came down to memory.
So we put the run record at the centre of the product. Once the environment, the time each case ran and the fact that the attached files have not changed are all on the record, the argument runs on the record instead of on somebody's word.
Slots came from the same place. When it is written up front how many testers a job takes, you spend your evening on it knowing what you are competing with. Invisible competition is the twin of invisible labour.
We work in four job types today: web, mobile, desktop and embedded. We keep the list short because each one needs different evidence, and we would rather learn that in the field before opening the next.
Tell us something from the field
If you have had a test report turn into an argument, we want to hear about it. These conversations are how the product gets built.