| || |
A few days ago I created a thread but I'm willing to share some info about our Dev/QA department:
-90% is manual testing and 10% is automated (started to automate some product areas lately).
-There are about 10 developers and 10 testers (everyone is fairly experienced).
-We work in the same office & most things are done face-to-face or through meetings.
-There is a network drive/intranet which hold functional/technical specs, docs about the product, and some QA standard cases. But, no official collaboration tool. I'm not sure if this is common in a dev/qa department?
-QAs are not required to write a user matrix but we explain our test coverage in the TFS history and close it once the issue has been verified.
-Each tester is responsible for their areas. But, individual testing notes are not shared (kept within their own PC). QA talk to developers and sometimes acquire valuable information which is not mentioned in the spec but is not shared. Is this common?
There might be something missing in the dev/qa department.
1.) Is "confluence" useful in small teams? Does confluence work as an individual piece of software? We use TFS right now (don't have JIRA)
2.) A lot of fellows on this forum suggest "confluence". What is so unique about this than a corporate network drive, Office 365, or google docs? I read a few articles online that people don't like to share knowledge for reasons such as promotion and secure their position. Some companies like to have 1 person to become the guru than every team members to be the all-in-one person.
3.) Do you know any common QA software tools for manual testing? (enterprise software)?
4.) How does your company minimize the number of reported bugs? (our release cycle is super fast 1 or 2 months. it include enhancements and significant changes. QAs barely make it to a final pass but 1st/2nd level pass. Is it common to see a lot of bugs reported?)
I should say there is no panacea against the bugs. There are plenty of manual testing platforms, which allow you to hire remote testers, as many as you need regardless the development team size. Try Ubertesters service.
Originally Posted by Tester850
1) They would test your app on the real devices, not just emulators.
2) More efficient bug reporting due to SDK integrated with bug-tracking systems (including JIRA)
3) Better feedback from testers provided with imbedded screenshot editor. QAs could send you a screenshot right from the device, with bug spotlighted. Besides this SDK automatically collects all necessary data about device - OS, device model, screen resolution and so on.
Take a look Features » Ubertesters