Selenium vs Figma: A Clear Comparison for Beginners

A simple Selenium test in Python:

from selenium import webdriver
from selenium.webdriver.common.by import By
from selenium.webdriver.common.keys import Keys
import pytest

@pytest.fixture
def driver():
    driver = webdriver.Chrome()
    yield driver
    driver.quit()

def test_search(driver):
    driver.get("https://example.com")
    search = driver.find_element(By.NAME, "q")
    search.send_keys("selenium")
    search.send_keys(Keys.RETURN)
    results = driver.find_elements(By.CSS_SELECTOR, ".result")
    assert len(results) > 0

What this does:
• Opens a browser
• Finds an element by selector
• Enters text, submits a form
• Checks that results appear
• Closes the browser

The work is mostly:
• Locating elements reliably
• Handling waits and timing
• Structuring tests so they are maintainable
• Reporting failures clearly

What an automation tester does daily:

MORNING
• Review CI results from overnight test runs
• Investigate failed tests (real bug or flaky test?)
• Fix locators or waits that broke after a UI change

MIDDAY
• Write new test cases for features in the sprint
• Extend the framework for a new module
• Pair with developers on testability

AFTERNOON
• Review test coverage for upcoming release
• Update test data and documentation
• Attend sprint ceremonies

The day is a mix of:
✓ Code writing
✓ Debugging (often timing issues)
✓ Communicating with dev and product teams
✗ Not design work

If you enjoy coding, debugging and the
satisfaction of making flaky tests reliable,
this career fits well.

A typical Figma design workflow:

1. FRAMES
   Create frames for each screen
   (mobile, tablet, desktop)

2. LAYOUT
   Use auto-layout for consistent spacing
   Set up grids and constraints

3. COMPONENTS
   Build reusable buttons, cards, inputs
   Use variants for states (default, hover,
   disabled, loading)

4. DESIGN SYSTEM
   Colour styles, typography styles,
   spacing tokens

5. PROTOTYPING
   Link screens to simulate user flows
   Add transitions and interactions

6. HANDOFF
   Share the file with developers
   Use dev mode to inspect CSS values

7. FEEDBACK
   Comment directly on frames
   Iterate based on user testing

Most of the work is visual and structural —
deciding what belongs on the screen and how
users move through it.

What a UI/UX designer does daily:

MORNING
• Review design feedback from stakeholders
• Update screens based on user testing insights
• Review tickets from developers

MIDDAY
• Design new screens or flows in Figma
• Work on component variants
• Pair with product managers on requirements

AFTERNOON
• User research synthesis
• Prototype a flow for the next review
• Hand off updated designs to dev

The day is a mix of:
✓ Visual design work
✓ User flow thinking
✓ Communicating with product, dev and users
✓ Prototyping and testing
✗ Not heavy coding

If you enjoy visual craft, user empathy and
solving flow problems, this career fits well.

A one-week test to decide between them:

DAY 1–2: SELENIUM
• Install Python and Selenium
• Write a script that opens a site and
  clicks a button
• Try to add an assertion
• Notice how you feel while debugging

DAY 3–4: FIGMA
• Create a free Figma account
• Recreate one screen of an app you use
• Try building a button component with
  a hover variant
• Notice how you feel while designing

DAY 5–7: REFLECT
• Which session felt more natural?
• Which one did you keep thinking about
  after the session ended?
• Which one would you still do if nobody
  paid you?

The answer is usually obvious after
one week of actually doing the work
instead of reading about it.

Do not decide from YouTube videos alone —
you will be watching, not doing.

Bad reasons to pick one over the other:

✗ "I heard QA pays more"
  Both fields have similar salary ranges
  at comparable seniority.

✗ "Design is easier"
  Figma is easier to start. Becoming a
  strong designer takes as much effort as
  becoming a strong automation engineer.

✗ "AI will replace testing"
  AI is changing testing, not replacing
  testing careers. AI is also changing
  design — neither field is immune.

✗ "I saw more QA jobs on Naukri"
  Both are high-volume. The right question
  is whether you can build a portfolio
  strong enough to get shortlisted.

✗ "My friend does QA"
  Your friend's preference is not your
  preference.

The one good reason:
You tried both briefly and one felt like
work you would choose to do — not work
you would avoid.

Selenium — 90-day plan:

WEEKS 1–4: FUNDAMENTALS
• Python or Java basics
• Selenium WebDriver: locators, waits
• Write 10 simple tests

WEEKS 5–8: STRUCTURE
• Page Object Model
• Test data handling (Excel/CSV)
• TestNG or Pytest
• Allure or Extent reporting

WEEKS 9–10: FRAMEWORK
• Build a framework for a public site
• Add data-driven tests
• Add CI (GitHub Actions)
• Document everything

WEEKS 11–12: JOB SEARCH
• Publish the framework on GitHub
• Write resume bullets with impact
• Apply to 25 QA/automation roles
• Practice framework design questions

Portfolio artifact:
One framework repo with README,
structure, CI and reporting.

Figma — 90-day plan:

WEEKS 1–4: FUNDAMENTALS
• Figma interface, frames, auto-layout
• Typography and spacing basics
• Recreate 3 screens from real apps
• Study one design system (Material or
  Apple HIG)

WEEKS 5–8: DESIGN THINKING
• Components and variants
• Prototyping and interaction states
• User flows and information architecture
• Start one case study

WEEKS 9–10: CASE STUDY
• Document a full redesign
• Include problem, users, decisions,
  before/after
• Test with 3 real users if possible

WEEKS 11–12: JOB SEARCH
• Build a portfolio page (Figma site or
  Framer)
• Practice presenting your work
• Apply to 25 UI/UX roles
• Get 2 peer reviews on your portfolio

Portfolio artifact:
2–3 case studies with process and
before/after, not just screenshots.