|
-
Retired SCORM Guru
QA Bug Reporting
I've inherited part of my company's QA process, where testers report needed modifications (not bugs) or ides for future enhancements for our web-based product.
The existing system, is to have the tester screenshot the item, print it out, add notes, and put it in a folder on my desk. However, when I go to prioritize and track lists, I don't have the original screenshot.
We have an internally built bug-reporting tool that allows for file uploads, but it's already overcrowded and confusing.
Can anyone recommend a tool, book or process to help me figure out how to manage this better? Thanks.
"What really bugs me is that my mom had the audacity to call Flash Kit a bunch of 'inept jack-asses'." - sk8Krog
...and now I have tape all over my face.
-
pablo cruisin'
Here's an open source solution I use for all my freelance work.
http://www.mantisbt.org/
"Why does it hurt when I pee?" -- F. Zappa |
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|