Quality assurance / testing communities?
I've been developing a test plan / test case management tool and am nearing the point where I will release version 1.0.
Can anyone point me to any online communities of software testing / quality assurance personnel that I might not already be aware of?
Thank you
-
Do you integrate with issue trackers (FogBugz or trac for example) and revision control software (SVN and Git for example)? I can't imagine paying significant money for this kind of thing without integration into all the other tools we use for development. – Tim J 14 years ago
-
Yes. I've considered publishing a road map, but I have mixed opinions about publishing it. In the near term, integration with most web or intranet based issue trackers like FogBugz, Trac, OnTime, etc and with VCS like SVN will be supported. For VCS integration, you will be to associate a SVN revision (or possibly a range) with a build. For issue trackers, first you will be able to associate a defect id with a test plan step. I would also like to be able to create a new defect from a test plan step, but that may not be possible with many issue tracking systems. – Consult Utah 14 years ago
-
Any other integration points that you think might be useful? Thanks! – Consult Utah 14 years ago
-
That all sounds good. You might want to make the integration via a public API so that not all the work to do integration is placed on you. This way your clients or the partners can write the plugins/etc. – Tim J 14 years ago
2 Answers
Are you aware of uTest.com?
Bob Walsh's podcast on this topic is great:
-
I was going to give the same answer. The podcast is great and uTest sounded really promising. – Reid Wilson 14 years ago
-
Thanks guys - I'll take a look. – Consult Utah 14 years ago
Follow the numbers - number will guide good QA decision making.
You did not mention requirements reviews or design reviews, or any other QA steps. Have these been done? The numbers show these QA steps are more effective (several times more effective) than "software testing". It does not matter what stage you are at, even if you have the code done, do these steps before you do "software testing". (This is the advice Tom Gilb gives, and having been there and done that, I would agree with him).
