Ask what you are stuck on, and answer what you know. Other SDETs vote for the best answers.
21 questions in Test strategy (page 1 of 2)
What strategies and code patterns should SDETs evaluate during developer PR reviews to enhance application testability?
How do I test AI/LLM-powered features where outputs are non-deterministic?
How can I use LLMs (ChatGPT, Claude, Copilot) to write and maintain tests without trusting them blindly?
How do I push back when I'm told to "just test it quickly" before a release?
How do I test in production safely (feature flags, canaries, observability)?
What is shift-left testing in practice, and how do I get involved before code is written?
How do I write a good bug report that developers actually act on?
How do I do exploratory testing well, and how do I document it?
How do I write effective test cases and choose between boundary value analysis, equivalence partitioning and decision tables?
What quality gates should block a release, and who decides?
How do I test with Docker and Testcontainers instead of shared staging environments?
How should I manage test data: seeding, factories, synthetic data or production copies?
How do I cut a two-hour regression suite down to 15 minutes?
Tests pass locally but fail in CI: what are the usual causes?
Should I retry failed tests, quarantine them, or delete them?