Apr 23
Access claim credentials strictly limited to one credential claim per tester
I want to make this suggestion regarding the access claim credentials which are required in some test cycles. Each credential has been made for testers to use specifically in that test cycle, which we all know a tester is almost fully handicapped without access. We are given the instruction to claim one credential, use and release once done, with the option to keep the used credential for another tester or mark as expired if it cannot be reused.I am raising awareness for this feature because most testers horde the credentials and claim multiple they don't use, making it impossible for other testers to participate in that test cycle and if eventually a claim gets released it's already used completely and should be filed as expired but it isn't and is kept in the claims list even though it's no longer useful in the test cycle. This can be frustrating to other testers and would make a tester reluctantly leave the test cycle, which is very unfavorable for the tester due to the limited invites being sent out weekly.The test cycle I participated in today *Test \#149035* had a tester who claimed 4 credentials and was completely unresponsive in the chat community, suggesting this tester was not even active in this test cycle but stood as an obstruction to other testers which is not only a violation of the clearly stated instruction (All testers are allowed one claim at a time and should release a credential once done for other testers to use), but highly unfair to the rest of the group, and not even being active puts the cherry on top for being incredibly insensitive. Earlier this year a tester claimed 8 credentials and went offline which was ridiculously frustrating.I am writing to suggest a stricter approach in the access claims, if possible making a tester able to claim one credential at a time like the bug reproduction feature. I also suggest educating testers on why it's important tagging a credential as expired when it can't be used by other testers anymore, because leaving an expired credential open confuses the system and makes it hard for a solution for more access claims to be provided to combat the already established problem of limited access claim credentials. This would not only level the playing field and keep testers happy, it would also improve the quality of testing and result in a thorough sweep of the presented site or app, making the test cycle a success. I hope this is considered because it is a recurring issue in our community.
Closed
Hello Esther! Thank you very much for bringing this important point to our attention. We understand that testers may sometimes encounter difficulties claiming accounts for testing purposes. At the same time, in some cases, a tester may need two or more accounts to properly test a specific product feature or user flow. To help improve this situation, the Customer Success Manager will ask the customer to add additional credentials when needed. Also, if all accounts are occupied during a testing cycle and testers are unable to claim them, Team Leaders will reset credentials when possible. We hope these measures will help reduce account claiming issues and make the testing process smoother for everyone. Thank you again for your valuable note. We truly appreciate your feedback and would be happy to hear more suggestions from you on how we can continue improving the platform.