
QADeputy
Test Smarter With QADeputy
We launched our marketing site and as part of that officially launched the product for customer use. While things were 'launched' we still had to begin the process of getting the word out, which can be a daunting task. We shared with our circles, posted on various sites (i.e. BetaList, BetaPage) and created social media accounts to start to draw in visitors.
Frustrated with the lack of tools available to solve my problem I sketched out my ideal product. I started with the basic functionality that existing platforms had (as I still needed that) and then sketched out the integrations/tooling that would ultimately solve the problem.
1 Like
Comment
After 4 months of development we had a product we could now start to use internally for basic test management. We began using processes in parallel to beta our own product and at the same time get the stuff done that needed to be done. We iterated on bugs and features developed.
1 Like
Comment
About
We built QADeputy because the test management tools didn't fit the bill for our own internal testing needs. We needed plug and play integrations with communication, bug tracking, and automation tools.

Comment