Introduce uniform standards for accept bugs between TL.
complete
AV-Master
Each team leader has his own criteria for making bugs. The same bugs different TL reject for opposite reasons.
Already, many times the bugs that some TL forwaded and the customer accepted were rejected by other TL. One TL considers the error visual, the other considers the error as functional.
TestIO academy rarely help reach agreement.
Tetiana Yezerska
complete
Ensuring a uniform rating across the team is a challenging task due to individual experiences and assessments. This challenge is particularly prevalent in areas where more than one person is involved in the assessment process. However, our ongoing efforts and implemented measures aim to address these complexities and promote consistency in ratings.
To ensure more uniform ratings across team members, we have implemented several measures:
Bug Assessment Sheet: A standardized form for assessing bugs to maintain consistency in evaluation.
Internal Rules for Team Leaders: Guidelines for team leaders to follow, ensuring a unified approach to rejections and exceptions.
Internal Reviews of Team Leaders: Regular evaluations of team leaders' performance with suggestions for improvement.
Internal Channels for Team Leaders: Dedicated channels for team leaders to discuss and resolve rating discrepancies.
Regular Reviews of Team Leaders' Work: Ongoing assessments of team leaders' performance, including key performance indicators (KPIs) that highlight areas for improvement.
Internal Investigations of Complaints: Investigations into any complaints regarding team leaders, ensuring fair and consistent treatment.
Training and Advice for Team Leaders: Training sessions and advice based on investigation outcomes to support team leaders in maintaining uniform ratings.
These measures are part of an ongoing process to continually improve the uniformity of ratings across the team.
Afgan Sofyan
It's actually could disturbing my perception of bugs, which I'm still learning as a greenhorn. I believe many are quite frustrated by this.
Paul.D
Obviously, because of this inconsistency, sometimes I have to know the character of the TL (handling for that error) instead of focusing on the exact severity of the error. Example: TL A considers issue "1" as severity A', but TL B considers it as severity B' (inconsistent); sometimes I try to dispute but also get a rejection (and get another answer). New comment from team dispute - here it is considered C'). So same issue (same root cause), I get 3 results as A', B' and C'
ted
Paul.D: Everywhere friends work, then the testers suffer.
Orukpe “Emmanuel” Iyore
This issue seems to be getting worse: many bug rejection reasons are just copy-paste and some Team Leaders don’t even reply when you ask more clarity on the rejection reason.
Bug dispute will most times take TL’s side instead of providing an objective and neutral response.
This issue is eroding tester enthusiasm and productivity.
Test IO please do something!
ted
One of the problems on the platform is dumb team leaders who have very little experience in testing.
Thanh Nhut Nguyen
This issue has not been improved yet.
Creative Mind
Yes, It should be implemented because Yesterday, I submitted two same suggestions in two different tests, and the test's instructions were also the same, 1 bug is rejected by the Team leader with a different comment but one bug is accepted by the Team Leader (Two Different Team Leaders). Same in the last month, I and my fellow tester submitted the same bugs in two different tests, and the instructions were also the same, but my fellow tester report was accepted by the Team Leader, and my bug rejected by the team leader with comment
It's not a bug
even I submitted the dispute and gave the link of both bugs for comparison and dispute was also not accepted even the issue same to same and that is the reason I cannot submit the disputes. Respected Test IO Team, Please review the suggestion of AV-Master
and clear the concept of rejection. Thank youEvgeniya Graich
Hello eveyone, have you noticed improvements in this field recently?
ted
Evgeniya Graich:
Very little.
- Propose to create a center of unified solutions on the platform.
- There are also some rules on the platform that create a battle between the tester and the team leader, which should not be!
ted
Evgeniya Graich:
- Please also tell the team leaders what placeholder is and what pretesting is. Not all team leaders follow the generally accepted rules about placeholders, and thus promote and protect cheaters.
- Any crash report, must contain a log. Even if the application closes instantly.
- For one team leader to share through a social network is one single bug, even if a bug is added for another social network. For another team leader, all bugs associated with different social networks are accepted.
- Why for different team leaders, the bug is high, as well as for the customer, but for another team leader, the bug is low?
- There are cases when the tester waits (1~10h) for an answer using the chat cycle.
- One team leader writes in a cycle chat about the need to reproduce a bug, another team leader simply rejects the bug, although there are still places for reproductions, and the negative reproductions themselves were sent from a completely different operating system.
L
Leena Hegde
Evgeniya Graich: I find No improvements.
Basit
Evgeniya Graich: NO!!!!, I recently get rejection.
Evgeniya Graich
in progress
Veronica Aides
hi, i have other suggestion,
I would suggest that "Type" of bug should be able to edit for the TL with the chance to change if this is not well selected by the tester, this will help testers if they make a mistake in the type of bug they submit. Is not so bad after all, if the report is well written and the bug is good.
if the bug seems to be good enough and is worth to send customer, the TL shouldn't reject it just because it didn't have the correct type (content or functional or visual ) in the report.
In this situation all the team looses, the customer (because the bug is not forwarder to him because was rejected by TL) , the tester, because after a lot of work,has a not paid bug, and also the TL because in the tester community this is not well accepted and is frustrating.
Please reconsider the possibility that the TL acts as a "last" reviewer who helps tester community to grow and help tester to write more and more good reports.
ted
Veronica Aides: You're right. Today's system is slightly misconfigured. It seems that this is a battle.
Load More
→