# How to plan move from manual testing profile to automation testing and getting job

**URL:** <https://club.ministryoftesting.com/t/how-to-plan-move-from-manual-testing-profile-to-automation-testing-and-getting-job/63900>\
**Category:** Discussions\
**Tags:** learning, automation, mentoring, career-development\
**Created:** [5 December 2022 00:25 UTC](https://club.ministryoftesting.com/t/how-to-plan-move-from-manual-testing-profile-to-automation-testing-and-getting-job/63900 "2022-12-05T00:25:59Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![charanjit250](https://avatars.discourse-cdn.com/v4/letter/c/f17d59/32.png) [@charanjit250](https://club.ministryoftesting.com/u/charanjit250)\
**Post date:** [5 December 2022 00:25 UTC](https://club.ministryoftesting.com/t/how-to-plan-move-from-manual-testing-profile-to-automation-testing-and-getting-job/63900/1 "2022-12-05T00:25:59Z")

</div>

Hello Everyone, Hope you have been keeping well.

How will you plan daily activities for your journey to become automation tester from manual profile?

Moreover, I want to collaborate with someone who wants to learn automation testing so that we can learn together, I believe two different brains definitely make a huge difference:)

I am reachable at below LinkedIn address.

[linkedin.com/in/charanjit-singh-89a499b3](http://linkedin.com/in/charanjit-singh-89a499b3)

---

<div class="post-metadata">

**Author:** ![testrigor](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/testrigor/32/10493_2.png) [@testrigor](https://club.ministryoftesting.com/u/testrigor)\
**Post date:** [8 December 2022 20:58 UTC](https://club.ministryoftesting.com/t/how-to-plan-move-from-manual-testing-profile-to-automation-testing-and-getting-job/63900/2 "2022-12-08T20:58:14Z")

</div>

Hi @charanjit250 ,

Here is the key concepts of automation and key best practices for manual testers: [Test Automation Best Practices - testRigor Codeless Test Automation Tool](https://testrigor.com/blog/test-automation-best-practices/)  
Feel free to use [testrigor.com](http://testrigor.com) free version for practice, this is precisely what it was created for.

Hope it helps,  
Artem.

---

<div class="post-metadata">

**Author:** ![sebastian\_solidwork](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/sebastian_solidwork/32/11076_2.png) [@sebastian\_solidwork](https://club.ministryoftesting.com/u/sebastian_solidwork)\
**Post date:** [9 December 2022 08:45 UTC](https://club.ministryoftesting.com/t/how-to-plan-move-from-manual-testing-profile-to-automation-testing-and-getting-job/63900/3 "2022-12-09T08:45:23Z")

</div>

Ill stay a tester and will do automation as well as “manual” aka exploration.  
Automation is just a tool to help your exploration.  
And even with a heavy focus on automation you will have chunks of exploration. Guess what you do when you find bugs during the automation?

Can we please use manual lesser and have no implicit binary choice of “manual vs automation”?

Here is a brief description how advanced my development skills (which includes automation):

> [@Coding for newbie testers](https://club.ministryoftesting.com/t/coding-for-newbie-testers/63473/10):
>
> any scripting language of a OS as they are often needed for different tasks: CMD, Bash, Powershell Groovy: is used in different tools to fill the gaps (e.g. SoapUI and Katalo) and is a full OOP language which can be written in a script style (no class and method definition needed). Due to its dynamic typing is very flexible. Further it has many useful additions (e.g. a own DSL for time related topics e.g. 1.day + 2.hours -3. minutes) and simplification. It’s also compatible to Java and let you …

---

<div class="post-metadata">

**Author:** ![conrad.connected](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/conrad.connected/32/10123_2.png) [@conrad.connected](https://club.ministryoftesting.com/u/conrad.connected)\
**Post date:** [9 December 2022 11:24 UTC](https://club.ministryoftesting.com/t/how-to-plan-move-from-manual-testing-profile-to-automation-testing-and-getting-job/63900/4 "2022-12-09T11:24:23Z")

</div>

If, if was doing this today would just follow the TAU (test automation university) courses or other applicable online trainers. But personally if you want to learn how to program, you really need to find a personal project that interests you. Usually this involves writing a multiplayer computer game using the target language and platform as a way to keep interest. For me, I practice my coding skills building a home automation system for example. Everyone has their own way of making learning fun, find yours.

I think the bigger elephant in the room to becoming a test automation engineer, is that most of the test automation training courses miss some big areas that SDETs typically spend a lot of time in just working out how to automate parts of their environments. Stack overflow is full of questions by system admins and test engineers trying to do things like automate app installations. Basically in how to prepare test machines and do test setup properly. How to create a clean test environment /sandbox is not taught often enough. Even web applications need realistic environments, it’s not just desktop applications that need to make sure tests run in a clean linux/windows machine. Manual testing does prepare you for some of this, but once you automate, a lot of security hurdles jump up in your way. You suddenly have to become an expert in areas you might not have before, like how to configure VLAN’s. Or how to isolate tests that now will run at the same time as each other on a test farm, where before they would run manually one at a time.

Sebastian has dropped a few good hints above already, but keep it fun, and good luck.

---

<div class="post-metadata">

**Author:** ![sebastian\_solidwork](https://sea2.discourse-cdn.com/flex020/user_avatar/club.ministryoftesting.com/sebastian_solidwork/32/11076_2.png) [@sebastian\_solidwork](https://club.ministryoftesting.com/u/sebastian_solidwork)\
**Post date:** [9 December 2022 11:42 UTC](https://club.ministryoftesting.com/t/how-to-plan-move-from-manual-testing-profile-to-automation-testing-and-getting-job/63900/5 "2022-12-09T11:42:14Z")

</div>

> ~~Manual~~ Testing does prepare you for some of this, but once you automate, a lot of security hurdles jump up in your way.

Fixed 😉

I agree on everything.  
Automation is way more than development.

---

<div class="post-metadata">

**Author:** ![denngrck](https://avatars.discourse-cdn.com/v4/letter/d/9fc29f/32.png) [@denngrck](https://club.ministryoftesting.com/u/denngrck)\
**Post date:** [9 December 2022 12:25 UTC](https://club.ministryoftesting.com/t/how-to-plan-move-from-manual-testing-profile-to-automation-testing-and-getting-job/63900/6 "2022-12-09T12:25:10Z")

</div>

We’ve collected various resources and ideas on becoming a test automation engineer that might be useful. IMO there’s no way around learning how to program if you want to contribute to a larger test automation project. And likewise it’s important to get familiar with other DevOps tooling, including source control and CI pipelines.

> **[Learning Test Automation: Becoming a Test Automation Engineer - Testmo](https://www.testmo.com/guides/learning-test-automation)**
>
> Learning test automation is a significant boost to your software testing arsenal. Our guide provides a great starting point to become a more productive and valuable software tester.

---

<div class="post-metadata">

**Author:** ![hiba](https://avatars.discourse-cdn.com/v4/letter/h/b3f665/32.png) [@hiba](https://club.ministryoftesting.com/u/hiba)\
**Post date:** [12 December 2022 11:47 UTC](https://club.ministryoftesting.com/t/how-to-plan-move-from-manual-testing-profile-to-automation-testing-and-getting-job/63900/7 "2022-12-12T11:47:09Z")

</div>

I can share something that I personally experienced: choose an application that you have access for, choose an automation tool and start learning by building test cases for that application. Try to spend some time per week to write few tests [spend some time to learn or fix something about the framework, the environment or the tool]
