How I break the shell with L.I.E.S
How I break the shell with L.I.E.S

When I thought of writing a new article, the first flash of inspiration came from the AMA I did last week with Tristan Lombard for the Testim Community.

During the AMA, Savanna Goodman asked an excellent question that correlates with our fear, imposter syndrome, and feelings that we may have while writing articles, and that led me to write this article.

“Everyone knows better than me”, “There may be tons of articles written on the same topic”, “Will people read my article if I also write about the same”.. Questions like these lead to writer’s block.

Then what makes us…


A Test Case shows the paths taken by a module, Use Case or functionality within the project. It serves as a basis for testers to run tests manually, but it can be created, too, in order to automate tests. In addition, Test Cases should cover as many situations as possible.

In short, a Test Case is a set of actions and the expected results for them.

What should you do?? -> Actions

The actions are the steps that will be performed by the tester/who run the test cases. These actions should lead to an expected result. They must always start…


From my 6 years of QA experience, I’ve heard a lot about how a QA should work.

I followed many of them but later knew that they were wrong. This article is to share some of those experiences and leave some suggestions on how to deal with them.

“QA is like the end user of a product”

Myth. This is still a belief that I see in some professionals. I had this mindset for a long time, that I was like the end-user who uses the product.

If I don’t know how the real user uses it, then how can…


If you are QA and find no bugs, this is not so bad. It’s time to break the conventional methodologies.
If you are QA and find no bugs, this is not so bad. It’s time to break the conventional methodologies.

If you are QA and find no bugs, this is not so bad. It’s time to break the conventional methodologies.

Until a few years ago, the QA was the guy who just planned and performed manual tests based on documentation and requirements, and that only happened in the testing phase.

We see and live an evolution in the role of QA, which becomes much more strategic within the team and close to business and product issues, while still running the tests. Programming skills for creating automated tests and shift-left testing approaches also enter this evolution package.

What triggered the motivation for this changes?

Manual tests focusing on…

Nithin SS

QA Lead, Test Automation @ Fave, Founder @ Synapse QA. Mobile & Web Automation Enthusiast. Get access to exclusive articles on: www.synapse-qa.com

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store