Tools and first-week setup
The tools a Selenium Automation Testing intern uses and how to set up your workspace in week one.
These are the main tools for Selenium Automation Testing tasks. You do not need all of them on day one; the Level 1 tasks tell you when to install each one.
- Selenium WebDriver
- Java (TestNG) or Python (pytest)
- Maven / pip
- Selenium Grid (Docker)
- Postman / REST Assured
- Cucumber
- Allure / Extent reports
Set up your workspace
- Create a free GitHub account if you do not have one, with a professional username, and set up your LinkedIn profile: every task is submitted with a LinkedIn post.
- Create one repository for the internship, for example selenium-automation-testing-internship, with a README that says who you are and what the repo holds.
- Keep one folder per task, named with the task number and title, so mentors find your work quickly.
- Commit small changes every day with clear messages. Your daily work report uses these commits as proof.
- Never commit passwords, API keys or personal data. Put secrets in a .env file and add it to .gitignore.
Your first tasks
| Task | What to do |
|---|---|
| Testing basics | In a repo named selenium-internship, explain manual versus automated testing, the test pyramid and when automation pays off. |
| Set up Selenium | Set up Selenium WebDriver with Java (Maven) or Python (pip) and open a browser to a practice site. |
| Locators | Find elements on a practice site with id, name, CSS selectors and XPath, and explain which locators are most stable. |
| Basic actions | Automate typing, clicking, selecting from dropdowns and checking checkboxes on a practice form. |