What Changed in the Automation Testing Job Market This Year

# 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_selenium():
    driver = webdriver.Chrome()
    try:
        driver.get("https://example.test/login")
        driver.find_element(By.ID, "email").send_keys("user@example.test")
        driver.find_element(By.ID, "password").send_keys("Test@123")
        driver.find_element(By.ID, "login").click()
        WebDriverWait(driver, 10).until(EC.url_contains("/dashboard"))
    finally:
        driver.quit()

# pip install pytest-playwright && playwright install
from playwright.sync_api import Page, expect

def test_login_playwright(page: Page):
    page.goto("https://example.test/login")
    page.get_by_label("Email").fill("user@example.test")
    page.get_by_label("Password").fill("Test@123")
    page.get_by_role("button", name="Log in").click()
    expect(page).to_have_url("https://example.test/dashboard")
# Playwright waits automatically for elements and assertions.

# pip install requests pytest
import requests

BASE = "https://jsonplaceholder.typicode.com"

def test_get_post_returns_expected_fields():
    r = requests.get(f"{BASE}/posts/1", timeout=10)
    assert r.status_code == 200
    body = r.json()
    assert {"id", "title", "body", "userId"} <= body.keys()

def test_create_post():
    r = requests.post(f"{BASE}/posts", json={"title": "qa", "body": "x", "userId": 1}, timeout=10)
    assert r.status_code == 201
    assert r.json()["title"] == "qa"

# .github/workflows/tests.yml
name: automated-tests
on: [push, pull_request]
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-python@v5
        with:
          python-version: "3.12"
      - run: pip install pytest requests pytest-playwright
      - run: playwright install --with-deps chromium
      - run: pytest -q --maxfail=3

Before accepting AI-generated test code:

[ ] Does every assertion check something meaningful?
[ ] Are locators stable (roles, labels, test IDs)?
[ ] No fixed sleeps; proper waits used?
[ ] Does it match the actual requirement, not a guess?
[ ] Does it run and fail when the feature is broken?
[ ] No secrets or real personal data included?
[ ] Would a teammate understand and maintain it?

# A test you did not write yourself must be proven to catch bugs.
# 1. Run it against working code -> it should pass.
# 2. Break the feature on purpose -> it should FAIL.

def total_with_gst(amount):
    return round(amount * 1.18, 2)

def test_total_with_gst():
    assert total_with_gst(100) == 118.0

# Now change 1.18 to 1.08 temporarily and rerun:
# if the test still passes, the test is useless.

Weekly job description tracker (10 listings)

Listing | Tool       | Language | API? | CI? | Mobile? | AI tools?
--------|------------|----------|------|-----|---------|----------
1       |            |          |      |     |         |
2       |            |          |      |     |         |
...

Count the ticks. The most frequent requirements in YOUR
target city and roles are your learning priorities.

My current skills: ______________________
Top 3 gaps from the tracker:
1. ________ -> plan: ________ -> proof: ________
2. ________ -> plan: ________ -> proof: ________
3. ________ -> plan: ________ -> proof: ________

Review after 4 weeks. Update the resume only when
the proof exists.

Portfolio upgrade for this year's market

[ ] UI suite in one modern framework (page objects/fixtures)
[ ] API test suite for a public demo API
[ ] Both running in a CI workflow
[ ] HTML or Allure report from CI
[ ] README explaining design choices
[ ] Note on how you reviewed any AI-generated code