Скачать с ютуб Gaslighting behaviour impacting QA team testing | Behavioural Challenges in Software Testing #7 в хорошем качестве

Gaslighting behaviour impacting QA team testing | Behavioural Challenges in Software Testing #7

What is Gaslighting in Software Testing? How to deal with Gaslighting in Software Testing? Statements which are Gaslighting Symptoms you should identify: Subtle suggestions by Product team that you “misunderstood" requirement Developer responses, “You’re overreacting; the performance benchmarks don’t account for edge cases Project manager arguments, “Our user base isn't that high. Are you sure this is relevant?” Vague functional requirement, but the product owner says, “It’s self-explanatory; just go with it.” Product manager dismisses a bug report, saying, “I don’t recall this issue in previous sprints. Are you sure it’s not a misconfiguration on your end? Product owner says, “I haven’t seen this issue; are you sure? Stakeholders comment, “Automation is always too sensitive. How accurate are these errors?” Team lead questions, “Are you overcomplicating the test scope? After a defect is found in production, your manager says, “This should have been caught during your testing.” A release is delayed, and your project lead comments, “Testing has been taking too long.” A requirement change causes a delay, and the blame starts to shift toward QA. Tech member says, "The bug isn’t that serious; let’s push it to the next release." Tech team member says, “It’s not affecting the main workflow; it can wait.” Developer comments, “Nobody’s going to notice that Tech lead comments, “It’s minor. We don’t need to worry Manager remarks, “We could’ve stayed on schedule if QA had tested faster. Test environment wasn’t fully set up, impacting your testing schedule, and the project manager says, “QA should have flagged this sooner.” Respond with, Mid-sprint requirement adjustments caused test case rework, and the product owner comments, “This could’ve been caught if QA was more agile.” A developer insists that an intermittent bug is negligible, but your instinct tells you otherwise You observe a pattern where certain feature releases frequently encounter defects, but a project lead brushes it off as "normal You catch multiple UI regressions in a new build, but a team member says, “It’s expected with new features.” Strategies: 1. Trust Your Gut: Prioritize Facts Over Manipulation 2. Use Assertive Phrases: Stand Firm In Your Experience 3. Shift Focus To Future: Move Beyond The Blame Game 4. Minimizing Bugs to Avoid Accountability 5. Shifting Blame for Missed Deadlines Lets see how in detail in video