Stop 06 · Programming Fundamentals for AutomationTopics · 7/10

Version Control (Git) for Testers

In short

Test scripts are code, and code changes every day. Git keeps a history of every change, so you can see who broke the login test and roll it back in seconds.

Enough Git to track changes to your test scripts and collaborate with a team — commit, push, pull, and basic branching, without needing full software-engineering-level Git mastery.

The purple blob flips through a photo album showing a clay pot at different stages.

Think of it like this

The progress photo album

A potter clicks a photo at every stage: lump of clay, shaped pot, painted pot. If the paint goes wrong, she knows exactly what it looked like before. Each Git commit is one such photo of your test project.

Watch it happen

Your daily Git loop

Your laptop

Local repo

GitHub

git pull

1/5Start the day by pulling teammates' latest changes.

The big ideas

What you need to know

Commit = snapshot

Each commit records what changed, who changed it and when. Small commits are easier to undo.

Branch for new work

Make a branch like add-checkout-tests. Main stays stable while you experiment.

Review before merge

Pull requests let someone check your tests before they run for the whole team.

Ignore secrets

Never commit passwords or API keys. Use a .gitignore and environment variables.

See it in code

Walk through the code

bash

1git clone https://github.com/your-team/ui-tests.git2cd ui-tests3git switch -c add-search-tests4 5# ...edit tests/test_search.py...6git status7git add tests/test_search.py8git commit -m "Add search tests for empty and long queries"9git push -u origin add-search-tests

1/3Copy the team repo and create your own branch for the new work.

The handful of commands you'll use 95% of the time as a tester.

Save yourself the pain

Common mistakes

Oops

Committing directly to main with messages like 'changes' or 'final2'.

Do this instead

Work on a branch and write messages that say what changed and why.

Oops

Committing a config file with real passwords inside.

Do this instead

Keep secrets in environment variables and add the local config file to .gitignore.

Your mission

Put your scripts under Git

~30 min

Quick check

You want to try a new set of tests without disturbing the working suite. What should you do first?

Go deeper

1Create a GitHub account and push a small automation script project to a repository.
2Practice a basic commit-push-pull cycle on a personal project.
3Learn to write a clear commit message describing what changed and why.