I hate poorly written test cases. Test cases should always be written as if the target audience has never seen or heard of your application before. #qa

Note to self: When testing an Amazon Echo app, always find a private room to test in. Nobody wants to hear you mess with Alexa’s head. #qa

As a #QA person, although I enjoy discovering a good bug, I love it when I test something and it just works.

If the test method blocks the feature under test from functioning then the feature cannot be tested. #qa

When there are two points in a ticket don’t send it back to QA with only one of them fixed. #qa

When you leave QA until the day before release you shouldn’t be surprised if blocking bugs are found that put the release in jeopardy. #qa

Always good to remember that case matters. Just had a session with a developer to research a bug and it turned out they were using lowercase when uppercase was needed. It’s an easy mistake but one to watch out for. #qa

When I write a note in a ticket asking questions about behavior I’m seeing in various platforms it should not be taken as a signal to release said ticket to production. Instead of one enhancement we now have three bugs. #qa

When you bypass #QA and release your code with a bug you make the whole team look bad when the bug is discovered. It’s not just your own reputation that’s on the line.