How Do I Know If Automation Testing Is Right for Me?

# test_login.py - Selenium 4 with pytest
# pip install selenium pytest
from selenium import webdriver
from selenium.webdriver.common.by import By
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC

def test_login_shows_dashboard():
    driver = webdriver.Chrome()   # Selenium Manager finds the driver
    try:
        driver.get("https://example-app.test/login")
        driver.find_element(By.ID, "email").send_keys("qa@example.com")
        driver.find_element(By.ID, "password").send_keys("test-password")
        driver.find_element(By.CSS_SELECTOR, "button[type=submit]").click()

        heading = WebDriverWait(driver, 10).until(
            EC.visibility_of_element_located((By.TAG_NAME, "h1"))
        )
        assert heading.text == "Dashboard"
    finally:
        driver.quit()

$ pytest -q test_login.py
F                                                    [100%]
_________________ test_login_shows_dashboard _________________

>       assert heading.text == "Dashboard"
E       AssertionError: assert 'Welcome back' == 'Dashboard'

1 failed in 4.21s

# Now the real work starts:
# - Did the product change the heading on purpose?
# - Or is this a genuine bug?
# Ask, check the ticket, then fix the test or raise a bug.

# fit_check.py - answer each question 0 (no), 1 (sometimes) or 2 (yes)
questions = [
    "I enjoy finding out why something broke",
    "I am willing to write code most days",
    "I can stay patient when a test fails for unclear reasons",
    "I like repeating a process until it is reliable",
    "I care about small details others miss",
    "I am comfortable learning tools that change every year",
    "I can explain a problem clearly in writing",
    "I like working closely with developers",
]

answers = [2, 1, 2, 1, 2, 1, 2, 1]   # replace with your own answers

score = sum(answers)
best = 2 * len(questions)
print(f"Score: {score} / {best}")

if score >= 12:
    print("Strong fit: start learning a framework and build a project.")
elif score >= 8:
    print("Possible fit: try a two-week trial before committing.")
else:
    print("Weak fit for now: explore manual testing or other roles first.")

weak = [q for q, a in zip(questions, answers) if a == 0]
for q in weak:
    print("Work on:", q)

$ python3 fit_check.py
Score: 12 / 16
Strong fit: start learning a framework and build a project.

HOW TO READ YOUR SCORE

12-16  Strong fit. The daily work matches what you enjoy.
 8-11  Possible fit. Your trial weeks will tell you more
       than this score.
 0-7   Weak fit for now. Consider manual testing, business
       analysis or support roles, and revisit later.

Any question you answered 0 is worth thinking about,
especially 'willing to write code most days'.

# test_discount.py - a first automated test you can run today
import pytest

def apply_discount(price, percent):
    if not 0 <= percent <= 100:
        raise ValueError("percent must be between 0 and 100")
    return round(price * (100 - percent) / 100, 2)

def test_ten_percent_off():
    assert apply_discount(1000, 10) == 900

def test_zero_discount_keeps_price():
    assert apply_discount(499, 0) == 499

@pytest.mark.parametrize("bad", [-5, 150])
def test_invalid_percent_raises(bad):
    with pytest.raises(ValueError):
        apply_discount(1000, bad)

$ python3 -m venv .venv
$ source .venv/bin/activate      # Windows: .venv\Scripts\activate
$ pip install pytest
$ pytest -q test_discount.py
....                                             [100%]
4 passed in 0.01s

# Now break it on purpose:
# change 900 to 950 and run again.
# Read the failure message slowly.
# Did finding the cause feel satisfying or annoying?
# Your honest answer is useful data.

TWO-WEEK AUTOMATION TRIAL (about 1 hour a day)

Week 1 - Python and pytest
Day 1  Install Python, create a venv, print and variables
Day 2  Functions, if/else, loops
Day 3  Lists and dictionaries
Day 4  Install pytest, write test_discount.py
Day 5  Add parametrize, break tests on purpose
Day 6  Write tests for a function of your own
Day 7  Rest or revise

Week 2 - One browser test
Day 8  Install Selenium or Playwright
Day 9  Open a practice site, find elements
Day 10 Write a login or search test
Day 11 Add explicit waits, remove sleep calls
Day 12 Put the test on GitHub
Day 13 Make it fail, debug it, fix it
Day 14 Fill the decision sheet

REFLECTION JOURNAL (2 minutes after each session)

Date: ______   Topic: ______________________

What I built or ran: _________________________
What failed:         _________________________
How I found the cause: _______________________

How it felt (circle one):
  energised   /   neutral   /   drained

One thing I want to learn next: ______________

Tip: after 14 days, count how many sessions
were 'energised'. That tells you a lot.

DECISION SHEET (fill on day 14)

Self-check score at start:  ___ / 16
Sessions marked energised:  ___ / 14
Tests I wrote that pass:    ___
Bugs or failures I debugged: ___

I enjoyed most: ____________________________
I disliked most: ___________________________

Decision:
[ ] Commit - join a course or plan structured study
[ ] Adjust - start with manual testing, add code later
[ ] Pivot  - explore a different role

Next action and date: ______________________