Skip to main content

Anyone can execute a test case, but not everyone can test

This post will tell you what I think about testing and test automation in general. I posted this on my Facebook last month but I just want to take note of it here as well.

Article that inspired me to write this: QA Career Path: What You Need To Know!

--

Anyone can execute a test case, but not everyone can test!!

 Excerpt from the article:
Numerous individuals are not comfortable with the professional growth prospects that are accessible in the software testing field. A few myths in the industry identified with picking Software Testing as a career are,
They are ridiculous as they sound:
- Development is superior to testing career. As anybody can test.
- Just the people who can’t code pick software testing as their career path.
- Pay rates will be less in software testing in contrast to software development.
- There won’t be any future growth in the software testing profession.
But all this isn’t a reality at all!

I admit that I also had these thoughts when I started my career on software testing. I don't have an idea about software testing since my college course focused on programming and I only knew about testing when I started working.

From my experience, I came to know that those who think too little of testing that are in the testing field fails because they don't even understand the concept and importance of testing. They thought it's simply something as following a test case. They never put effort to understand the business purpose and impact of the application itself and the specific functionalities so they only focus on one direction when testing. They never put effort to understand the technologies being used in the application in order to understand how it's made (and how to break it).

Then there's also testers in test automation field. It's good to be able to apply and develop automated test cases but I hope they and/or the company doesn't treat manual testers less than everyone. Manual testing can still be better than automation since they are able to explore more on the application and check corner scenarios, and is proven to have higher defect detection than automation. Also for test automation, it has to be done well in a sense of the test scripts should really be testing the application. I've seen many automated test cases that seems to be navigating only in the application instead of testing it. Test automation testers should keep in mind that they are testers first before being a technical person. The most important output is a working software, not the test automation coverage %.

I hope everyone in the testing field realizes how they are as important as the development team. Be proud and happy testing!
Labels:

Popular posts from this blog

Reframing how I identify bug root causes

It's been more than a year now since I've set up our bug tracking in JIRA. In there, I've set up an Issue Root Cause custom field where it had the following options: Incorrect coding Unclear / Missing / Incorrect Requirements Unclear / Missing / Incorrect Design Insufficient / Duplicated / Incorrect Testing Deployment Issue Environment Third-party issue My thoughts when I listed these as options is so that it would be easy to identify which team is responsible for the cause why we had that bug. They're pretty straightforward -  Incorrect coding  is of course when the developers didn't follow the expectations,  Unclear / Missing / Incorrect Requirements is because there's a gap in the requirement, and so on. And also, it's because that was the way it's done in my previous company so that's also my initial knowledge source. Recently, I've been reading a few articles regarding Shift Left, reducing silos, and generally how quality is a team activit...
Read more

QA Tools: Custom Test Case Generator in Google Sheet using Google App Script

When testers have to document test cases, it's usually done in the traditional format of putting all your test cases and steps in one sheet. Once it accumulates, for me it can be overwhelming to look at. It looks something like this: As a solution, I decided to make a tool that will help me focus on only drafting my test scenarios and look at my test cases one at a time. I'd like to share this here with everyone else who's like me. Hopefully, it can make your testing journey even a little better. Test Case Generator Tool This tool is for QA or non-QAs who need to write test cases. What it can do: Write your test scenarios in one tab Focus on writing steps for each test case one sheet at a time Generate an import file Generate a test execution document Sample test execution document: Scroll to the bottom to see how it works. Sheet Purpose Test Scenarios This is where you set the details for this test set/the project/story/epic where you're creating the test cases u...
Read more

A Bug's Life! Defect Management Process in Software Testing

First things first, what does a "bug" mean in the software development process? A bug is what we call a behavior that is different from what's expected based on the provided requirements. A tester's main purpose is to find and report bugs in the system as early as possible. In some companies, it's sometimes called a "defect". They actually mean slightly different if we go by the book. In this post, I'll be covering the lifecycle of a software bug which are issues that are found during the development phase. You're testing the system and you found a bug. What is the first thing you do? a) You immediately write a bug report b) You try to reproduce it c) You complain "How could this very obvious bug reach QA? Dev should've spotted this earlier ugh." The formal answer is B (I'll just let you figure out what's the informal answer), It's common for a QA to be gaslighted. "I cannot reproduce this bug.", "It doesn...
Read more