Update Module 2 and weeks readme.md

GayathriVenkatraman · GayathriVenkatraman · commit f1ccb4a3235d · 2025-12-07T08:22:11.000+01:00
diff --git a/courses/qa/test-automation/README.md b/courses/qa/test-automation/README.md
@@ -1,27 +1,25 @@
-# `Module Name`
+# TEST AUTOMATION
 
-This module is about `description goes here`
+Here you can find course content and the assignments for the Test automation module. This module basically focus on web app testing, modern UI automation, and new automation focuses (Accessibility & Performance).
 
 ## Contents
 
-| Week | Topic                                | Preparation                           | Session Plan                                          | Assignment                          |
-| ---- | ------------------------------------ | ------------------------------------- | ----------------------------------------------------- | ----------------------------------- |
-| 1.   | [`Session Title`](./week1/README.md) | [Preparation](./week1/preparation.md) | [Session Plan](./week1/session-plan.md) (for mentors) | [Assignment](./week1/assignment.md) |
+| Week | Topic                                       | Preparation                         | Assignment                        | Session Plan                          |
+| ---- | ------------------------------------------- | ----------------------------------- | --------------------------------- | ------------------------------------- |
+| 1.   | Web Testing with DevTools                   | [Preparation](week1/preparation.md) | [Assignment](week1/assignment.md) | [Session Plan](week1/session-plan.md) |
+| 2.   | Introduction to Test Automation with Playwright (TypeScript)                        | [Preparation](week2/preparation.md) | [Assignment](week2/assignment.md) | [Session Plan](week2/session-plan.md) |
+| 3.   | Building Automation Structure & Page Object Model (POM)           | [Preparation](week3/preparation.md) | [Assignment](week3/assignment.md) | [Session Plan](week3/session-plan.md) |
+| 4.   | Accessibility Testing Fundamentals & Playwright                          | [Preparation](week4/preparation.md) | [Assignment](week4/assignment.md) | [Session Plan](week4/session-plan.md) |
+| 4.   | Accessibility Testing Fundamentals & Playwright                          | [Preparation](week5/preparation.md) | [Assignment](week5/assignment.md) | [Session Plan](week5/session-plan.md) |
 
 ## Module Learning Goals
 
-> [!TIP]
-> Learning goals should be a list of outcomes, rather than a list of topics. For example, instead of "Synchronous vs Asynchronous", write something like "Explain the difference between sync and async code execution in JavaScript"
-
 By the end of this module, you will be able to:
 
-- [ ] `[action verb] [specific skill/knowledge]`
-
-## Prerequisites
-
-> [!TIP]
-> Some modules build on the learning goals of other modules. If that is the case, link them below. If there are no prerequesites, feel free to remove this section. Note that it is assumed that all foundation modules are a prerequisite of a specialisation course and its modules, so in that case you don't have to write them all out here :-)
-
-You should have completed or understand the learning goals in the following modules before proceeding:
-
-- [`Module Name`](https://example.com)
+- [ ] Understand web application architecture and common testing challenges.
+- [ ] Perform cross-browser and responsive design testing.
+- [ ] Learn UI automation fundamentals using modern tools (e.g., Selenium or Playwright).
+- [ ] Implement advanced automation practices like Page Object Model and CI/CD integration.
+- [ ] Conduct accessibility testing using tools like Axe or Lighthouse.
+- [ ] Perform basic performance testing and interpret key metrics.
+- [ ] Apply best practices for maintaining automated test suites.
diff --git a/courses/qa/test-automation/week1/README.md b/courses/qa/test-automation/week1/README.md
@@ -1,6 +1,6 @@
-# `Session Name` (Week `X`)
+# TEST AUTOMATION, Week 1
 
-This session is about `description goes here`
+In this session, trainees will learn the fundamentals of web testing using browser developer tools. We will cover client–server architecture, the structure of web pages (DOM, HTML, CSS, and basic JavaScript), and how to use DevTools effectively for testing. This week focuses on identifying common front-end issues and analyzing network requests.
 
 ## Contents
 
@@ -10,9 +10,13 @@ This session is about `description goes here`
 
 ## Session Learning Goals
 
-> [!TIP]
-> Learning goals specific to this session. These should be a subset of the module's learning goals, and expanded on in more detail if possible.
-
 By the end of this session, you will be able to:
 
-- [ ] `[action verb] [specific skill/knowledge]`
+- [ ] Understand client–server architecture and how web apps communicate.
+- [ ] Explore web elements: DOM, HTML, CSS, and JavaScript basics.
+- [ ]  Use Browser DevTools for testing:
+     - [ ] Elements tab for inspecting and modifying DOM/CSS.
+     - [ ] Console tab for debugging JavaScript errors.
+     - [ ] Network tab for analyzing requests and responses.
+- [ ] Identify common front-end issues QA can detect.
+- [ ] Practice inspecting elements and debugging console/network issues on a sample site.
diff --git a/courses/qa/test-automation/week2/README.md b/courses/qa/test-automation/week2/README.md
@@ -1,6 +1,6 @@
-# `Session Name` (Week `X`)
+# TEST AUTOMATION, Week 2
 
-This session is about `description goes here`
+In this session, trainees will learn the fundamentals of UI test automation using Playwright with TypeScript. We will cover why automation is important, how to set up the Playwright and Node.js environment, and basic TypeScript concepts for testers. This week focuses on writing and running your first Playwright test, understanding selectors and assertions, and executing tests in headed and headless modes.
 
 ## Contents
 
@@ -10,9 +10,12 @@ This session is about `description goes here`
 
 ## Session Learning Goals
 
-> [!TIP]
-> Learning goals specific to this session. These should be a subset of the module's learning goals, and expanded on in more detail if possible.
-
 By the end of this session, you will be able to:
 
-- [ ] `[action verb] [specific skill/knowledge]`
+- [ ] Understand why test automation is essential in modern QA.
+- [ ] Set up Playwright and Node.js environment for automation.
+- [ ] Learn basic TypeScript concepts relevant for testers.
+- [ ] Write and run your first Playwright test.
+- [ ] Understand selectors and assertions in Playwright.
+- [ ] Execute tests in headed and headless modes.
+- [ ] Automate a simple login flow using Playwright.
diff --git a/courses/qa/test-automation/week3/README.md b/courses/qa/test-automation/week3/README.md
@@ -1,6 +1,6 @@
-# `Session Name` (Week `X`)
+# TEST AUTOMATION, Week 3
 
-This session is about `description goes here`
+In this session, trainees will learn how to organize test automation projects for scalability and maintainability. We will cover test suite structure, reusing locators and actions, and introduce the Page Object Model (POM) design pattern. This week also focuses on creating Page Object classes in Playwright, understanding the benefits of modular test design, and an introduction to test reporting.
 
 ## Contents
 
@@ -10,9 +10,12 @@ This session is about `description goes here`
 
 ## Session Learning Goals
 
-> [!TIP]
-> Learning goals specific to this session. These should be a subset of the module's learning goals, and expanded on in more detail if possible.
-
 By the end of this session, you will be able to:
 
-- [ ] `[action verb] [specific skill/knowledge]`
+- [ ] Organize test suites for better structure and maintainability.
+- [ ] Reuse locators and actions across multiple tests.
+- [ ] Understand the Page Object Model (POM) and its advantages.
+- [ ] Create Page Object classes in Playwright.
+- [ ] Apply modular design principles for scalable automation.
+- [ ] Get an introduction to test reporting tools and practices.
+- [ ] Refactor previous Playwright tests into a POM-based structure.
diff --git a/courses/qa/test-automation/week4/README.md b/courses/qa/test-automation/week4/README.md
@@ -1,6 +1,6 @@
-# `Session Name` (Week `X`)
+# TEST AUTOMATION, Week 4
 
-This session is about `description goes here`
+In this session, trainees will learn the importance of web accessibility and how to test it both manually and through automation. We will cover WCAG standards, perform basic manual accessibility checks (keyboard navigation and screen reader basics), and automate accessibility testing using Playwright with Axe-core. This week also focuses on analyzing and reporting accessibility defects effectively.
 
 ## Contents
 
@@ -10,9 +10,10 @@ This session is about `description goes here`
 
 ## Session Learning Goals
 
-> [!TIP]
-> Learning goals specific to this session. These should be a subset of the module's learning goals, and expanded on in more detail if possible.
-
 By the end of this session, you will be able to:
 
-- [ ] `[action verb] [specific skill/knowledge]`
+- [ ] Understand what Web Accessibility is and why it matters (WCAG principles).
+- [ ] Perform manual accessibility checks: Keyboard navigation, Screen reader basics.
+- [ ] Automate accessibility checks using Playwright and Axe-core.
+- [ ] Analyze accessibility violations and report defects clearly.
+- [ ] Use Playwright to run basic accessibility checks on a sample site and identify violations.
diff --git a/courses/qa/test-automation/week5/README.md b/courses/qa/test-automation/week5/README.md
@@ -0,0 +1,22 @@
+# TEST AUTOMATION, Week 5
+
+In this session, trainees will learn the fundamentals of front-end performance testing and how modern tools like Google Lighthouse help QA teams ensure quality. We will cover key performance metrics, run Lighthouse audits, interpret reports, and explore automation options using Lighthouse CLI or Node module.
+
+## Contents
+
+- [Preparation](./preparation.md)
+- [Session Plan](./session-plan.md) (for mentors)
+- [Assignment](./assignment.md)
+
+## Session Learning Goals
+
+By the end of this session, you will be able to:
+
+- [ ]  Understand key front-end performance metrics:
+    - [ ] First Contentful Paint (FCP)
+    - [ ] Largest Contentful Paint (LCP)
+    - [ ] Total Blocking Time (TBT)
+- [ ] Learn what Google Lighthouse is and why it matters for QA.
+- [ ] Run and interpret Lighthouse reports for: Performance, SEO & Best Practices
+- [ ] Automate Lighthouse audits using CLI or Node.js module.
+- [ ] Analyze and report performance and accessibility scores from Lighthouse reports.
diff --git a/courses/qa/test-automation/week5/assignment.md b/courses/qa/test-automation/week5/assignment.md
@@ -0,0 +1,11 @@
+# Assignment
+
+> [!TIP]
+> The type of assignment you write will vary a lot depending on the module. But either way, all of the set up, instructions and tips should be captured in here.
+
+`Content goes here...`
+
+## Optional Tasks/Assignments
+
+> [!TIP]
+> If you have some extra tasks for the assignment, or additional assignments, that trainees can complete if they finish the rest, or want to push themselves, include them in this optional section.
diff --git a/courses/qa/test-automation/week5/preparation.md b/courses/qa/test-automation/week5/preparation.md
@@ -0,0 +1,17 @@
+# Preparation
+
+## Reading List
+
+> [!TIP]
+> If you have some great external resources, you might want to create an external reading list for trainees to go through before the session.
+
+Read/watch through this list of content before you come to the session:
+
+- [`Title`](https://example.com/) by `Author`
+
+## `Topic`
+
+> [!TIP]
+> Additionally, or instead of, you may wish to write your own pre-reading content. Be sure to keep it clear, consice, related to the learning goals - and think about using images and diagrams to make it easier to digest.
+
+`Content goes here...`
diff --git a/courses/qa/test-automation/week5/session-materials/example-session-material.md b/courses/qa/test-automation/week5/session-materials/example-session-material.md
@@ -0,0 +1,6 @@
+# Example Session Material
+
+> [!TIP]
+> This could be a markdown file, or pdf, link to google slides, or whatever format was used for the material. Be sure to include the source, if necessary, so future mentors can iterate on it!
+
+`Content goes here...`
diff --git a/courses/qa/test-automation/week5/session-plan.md b/courses/qa/test-automation/week5/session-plan.md
@@ -0,0 +1,28 @@
+# Session Plan
+
+> [!TIP]
+> The session plan is written to guide the mentor to prepare and run the session. Of course, trainees may come across and read this material. But it should be written as if you're speaking to a mentor.
+
+## Session Materials
+
+> [!TIP]
+> Previously used slides, docs or any other materials that future mentors could get value from should be listed here. If we don't have any (yet), this section can be removed.
+
+These are some examples of previously created materials by mentors that you can use yourself, or for inspiration.
+
+- [`Resource Name`, `@author`, `Team X`](https://example.com/)
+
+## Session Outline
+
+> [!TIP]
+> Write a plan for the order of topics, points to cover, examples, timings, exercises and any other useful info to guide the session.
+
+## Exercises
+
+> [!TIP]
+> Exercises might appear inside the Session Outline section if they are tightly integrated into the flow of the session. If you have more like a library of exercises that should be worked through in order, then you could also list them in a separate section here.
+
+## Optional Exercises
+
+> [!TIP]
+> If you have some extra exercises that trainees can complete if they finish the rest, or want to push themselves, include them in this optional section.
