uTest Platform: Updates and Feedback | Re: Platform Feature Requests

allysonburk wrote:

If the bug is clearly out of scope or a duplicate, usually the TTL can just reject it outright (depending on permissions and the request of the client). Pending rejection typically means the TTL is on the fence about an issue or they feel it is working as designed. The fact is, you can't really do anything until the bug is officially rejected and, as a TTL, I wouldn't want you discarding or editing an issue based on my recommendation in the event that I am wrong. This is why TTLs don't usually give you a reason for Pending Rejection.

Allyson - I understand where you're coming from (I recently had a bug go from pending rejection to approved as very valuable), but I agree that early feedback is a good thing. Its a good teaching tool. It allows the tester to a) augment the report if its not clear or b) change the focus and/or methods of testing if it looks like they're heading down the wrong path.

Communication has always been a problem at uTest - there's no way to have an informal 3 minute hallway conversation about a question (and Chat and Discussion Boards aren't always terribly responsive or appropriate). Since the TTL is in closer contact with the PM and customer they presumably are more plugged into more subtle nuances of product design / customer desires.

I don't like to file disputes - I'd much prefer clarifying/supplementing my report before it gets rejected (as I've done with you at least once) so I don't HAVE to file one.

Frank

---