Setting Up Your Environment

Why Environment Setup Matters #

A properly configured environment eliminates friction when you start practicing. Nothing kills motivation faster than spending an hour troubleshooting tool installation when you should be learning QA concepts.

This lesson walks you through installing everything you need. No programming is required — just downloading, installing, and verifying tools work correctly.

The QA Tools Ecosystem #

Here’s how the tools you’ll install relate to different types of testing:

You won’t use all tools from day one. Modules 1-4 mainly use a browser and Postman. Automation tools (VS Code, Node.js, Git) become essential from Module 5 onward.

Tool 1: Browser DevTools #

What it is: Built-in developer tools in every modern browser (Chrome, Firefox, Edge).

Why QA needs it: Inspecting page elements, monitoring network requests, checking for console errors, testing responsive layouts, and analyzing page performance.

Setup:

1. Open Google Chrome (recommended for this course) or your preferred browser
2. Press F12 (Windows/Linux) or Cmd + Option + I (Mac)
3. DevTools panel should open

Verify it works:

• Go to any website
• Open DevTools (F12)
• Click the “Elements” tab — you should see the page’s HTML
• Click the “Network” tab, reload the page — you should see network requests appearing
• Click the “Console” tab — type console.log("QA ready!") and press Enter

If you see “QA ready!” in the console, DevTools is working perfectly.

Key tabs you’ll use:

Tool 2: Postman (Free) #

What it is: A platform for building and testing APIs. The free version covers everything you need.

Why QA needs it: Testing REST APIs, creating request collections, validating response data, and automating API tests.

Setup:

1. Go to postman.com/downloads
2. Download and install the desktop app for your OS
3. Create a free account (or use the lightweight API client without an account)

Verify it works:

1. Open Postman
2. Click “New” then “HTTP Request”
3. Enter this URL: https://jsonplaceholder.typicode.com/posts/1
4. Click “Send”
5. You should see a JSON response with a post title and body

If you see JSON data with "userId": 1, Postman is working correctly.

Tool 3: VS Code (or Any Text Editor) #

What it is: A free, lightweight code editor by Microsoft. The most popular editor for QA automation.

Why QA needs it: Writing test scripts, editing configuration files, viewing test results, and working with Git.

Setup:

1. Go to code.visualstudio.com
2. Download and install for your OS
3. Open VS Code

Recommended extensions (install later, when you need them):

• Prettier — code formatting
• REST Client — send HTTP requests from VS Code
• GitLens — enhanced Git features
• Playwright Test for VS Code — run Playwright tests (Module 8+)

Verify it works:

1. Open VS Code
2. Go to File > New File
3. Type Hello, QA! and save it as test.txt on your desktop
4. If the file saves and opens correctly, VS Code is ready

Tool 4: Git #

What it is: A version control system that tracks changes in files.

Why QA needs it: Managing test code, collaborating with development teams, reviewing code changes (which often reveals where bugs are), and working with CI/CD.

Setup:

Windows:

1. Download from git-scm.com
2. Run the installer (default settings are fine)
3. Open Command Prompt or Git Bash

Mac:

1. Open Terminal
2. Type git --version
3. If not installed, you’ll be prompted to install Xcode Command Line Tools — accept the prompt

Linux:

1. Open Terminal
2. Run sudo apt install git (Ubuntu/Debian) or sudo dnf install git (Fedora)

Verify it works:

git --version

You should see something like git version 2.43.0 or newer.

Initial configuration:

git config --global user.name "Your Name"
git config --global user.email "your.email@example.com"

Tool 5: Node.js (For Later Modules) #

What it is: A JavaScript runtime that lets you run JavaScript outside the browser.

Why QA needs it: Running test automation frameworks like Playwright and Cypress, installing testing tools via npm, and running scripts.

Setup:

1. Go to nodejs.org
2. Download the LTS (Long Term Support) version
3. Run the installer

Verify it works:

node --version
npm --version

You should see version numbers for both. Node should be 18+ and npm 9+.

You won’t need Node.js until Module 8 (Test Automation), but installing it now saves time later.

Tool 6: Python (Optional) #

What it is: A programming language often used for test automation and scripting.

Why QA might need it: Some companies use Python-based test frameworks (pytest, Robot Framework). It’s also useful for data processing and scripting.

Setup:

1. Go to python.org/downloads
2. Download Python 3.11+ and install
3. Make sure to check “Add Python to PATH” during installation (Windows)

Verify it works:

python3 --version

You should see Python 3.11.x or newer.

Python is optional for this course. The automation modules focus on JavaScript/TypeScript with Playwright, but Python knowledge opens additional career paths.

Creating Your Course Folder Structure #

Create a dedicated workspace for the course:

qa-course/
├── notes/           # Your lesson notes
├── exercises/       # Exercise solutions
│   ├── module-01/
│   ├── module-02/
│   └── ...
├── projects/        # Larger practice projects
└── resources/       # Downloaded materials, cheat sheets

Quick setup via terminal:

mkdir -p qa-course/{notes,exercises,projects,resources}
mkdir -p qa-course/exercises/module-{01..12}

Or create the folders manually using your file manager — the structure is what matters, not the method.

Bookmarks to Save #

Save these resources for quick access throughout the course:

Troubleshooting Common Issues #

“Command not found” after installation: Close and reopen your terminal. On Windows, you may need to log out and back in. On Mac/Linux, run source ~/.zshrc or source ~/.bashrc.

Postman can’t connect: Check your firewall settings. Some corporate networks block Postman — try using your personal network.

Git asks for credentials every time: Set up SSH keys or use a credential manager. We’ll cover this in detail in the Git module.

Node.js version conflicts: If you have multiple projects needing different Node versions, install nvm (Node Version Manager) later. For now, the LTS version is fine.

Next Steps #

Your environment is ready. You now have everything installed to follow along with every lesson in the course. In the next lesson, we’ll look at QA career paths and salary expectations to help you set long-term goals.

Don’t worry if you don’t understand what each tool does yet — that’s what the rest of the course is for. Right now, all that matters is that they’re installed and verified.