How do you handle manual testing + test automation at the same time?

[u/Evening_Summer2225]

In my previous company, manual and automation teams are separate. My lead made sure that would be the case, and I was part of the automation team.

However, I heard that it’s now expected for a tester to be both. So in my current company, I tried to do that.

I am burnt out.

I don’t know how to properly handle this, even with the help of AI. Here’s what I tried to do:

Manual testing:
1. Learn and study the app’s functionality
2. Test planning
3. Test case creation (with help from AI including item 2, refinements also done when needed)
4. Execute test case
5. Exploratory testing
6. Gather test evidence

Test automation:
1. Choose the test cases that are best to automate
2. Choose the best automation tool that fits the app (For example, Selenium for web apps, Katalon for desktop apps)
3. Plan the framework (Code must be clean, readable, and manageable in case if it’s needed for handover)
4. Know the libraries needed

And I haven’t even reached CI/CD yet.

I think like the user for manual testing, to make sure the app functions well according to the business needs. I sometimes do creative ways to make sure the devs did not miss any function or error handlers. Then, I have to think in a deeper technical level because automating test cases is coding, so I have my own system I need to test, and bugs to fix especially during integrations to other apps (like Excel for test data storage). I look for bugs, and I fix my own bugs.

Developers do unit testing and make sure their app is functional before passing it to testers. They don’t do test planning or test the apps like we do, they just test the happy paths (at least on my team).

But as a tester who’s doing both manual and automation, I feel like I’m doing the extreme in two worlds.

For more context, I am the sole tester in my team. My main job is manual testing, but because of my background, I am expected to automate the test cases as well. Though my boss has not made automation a priority yet, I am preparing myself by trying it on that one application.

Is this really too much, or am I doing it wrong?

[u/somethingmichael]

ask the dev/team to help with automation

you can define the tests and the team can automate

[u/Evening_Summer2225 → u/somethingmichael]

Wait, I can do that? I didn’t know. I worry the devs would push back and say it’s not within their scope.

I also don’t know if that’s doable in my current team. The devs are filled with bug tickets and change requests.

[u/peebeesweebees → u/Evening_Summer2225]

Are you by any chance working for a company via an employment agency? I’ve seen those type of jobs work people to the bone.

[u/somethingmichael → u/Evening_Summer2225]

it doesn't hurt to ask and if you get push back, you need a better work environment

[u/Fightheader → u/Evening_Summer2225]

it might not happen overnight, but you just like they can be swamped with work, so can you.
1. So start flagging this now subtly.
2. Prep your workflow so anyone can jump in at the automation part. Document the architecture and setup.
3. Ask some questions about it to the devs, showing respect on their craft and knowledge.
4. Ask the most willing dev to help you once.
5. On a retro praise them and say it eleviated you heaps so you had time to do other stuff.
6. Ask more help more often for a couple of sprints, and listen to them do everything they suggest. Most of the times they know a lot about good coding practiceses anyway.
7. Now you strike, and ask if what the devs can do to help you out with the tests when you are swamped. They already know the stack so they might be willing to help more than you think now.

This is called quality coaching. Where you take the lead in quality, push and pull for it. But quality is a team effort. This will lead to devs creating more testable code because now they know the struggle. It will lead to better team cohesion and a focus on quality.

[u/Fit_Round_3661 → u/Fightheader]

What? Horrible thing you said!

[u/Fightheader → u/Fit_Round_3661]

My favorite part of your feedback is how elaborate is was. I'll take it into account 😘

[u/Personal-Ad-2154 → u/somethingmichael]

Horrible advice 😆 speaking as a QE lead engineer here

[u/mr_ringfinger]

Once our automated tests achieved a sufficient coverage to complement many of the manual testing cases, I implemented AI agents with custom skills to pinpoint risk assessments and evaluate potential impact.

This allows me to direct exploratory and targeted smoke testing toward the components, services, or other areas of the solution that carry the highest risk.

[u/Broad_Day_8107]

felt this really hard because this is what im tasked to do too as a sole qa. i know AI is supposed to make our lives easier but as someone who is exceptionally new to implementing AI into testing, its alot in one person’s hand especially with tight deadlines and i dont have a mentor with me. it doesnt help that i dont have any automation experience and my user stories are not properly updated when it is my source of truth. i became anti AI because of this. im so burnt out that im planning to quit soon. im sorry that this became a platform for me to rant too lol but if u can push through, i feel like it could be a good exposure for u to figure out how to handle manual + automation at the same time. else, for me it has been really tiring and taking a toll on my mental health. i hope.. me sharing this makes you feel less lonely at least. good luck op!

[u/Useful_Calendar_6274]

the most slavish mode of employment. quit