From cf8a9137d0eac5f46b50d03acc79cb30b2f86768 Mon Sep 17 00:00:00 2001 From: Mohak <143473709+Mohak51234@users.noreply.github.com> Date: Thu, 20 Aug 2026 00:09:49 +0530 Subject: [PATCH] Added table of contents --- Acceptance-Tests.md | 26 +++++++++++++++++++++++++- 1 file changed, 25 insertions(+), 1 deletion(-) diff --git a/Acceptance-Tests.md b/Acceptance-Tests.md index c2e83023..9c483bee 100644 --- a/Acceptance-Tests.md +++ b/Acceptance-Tests.md @@ -1,4 +1,28 @@ -# Introduction +## Table of contents + +* [Introduction](#introduction) +* [Files and Directory Structure](#files-and-directory-structure) +* [How to run the acceptance tests](#how-to-run-the-acceptance-tests) +* [How to write new tests for a specific user](#how-to-write-new-tests-for-a-specific-user) +* [Migrating Acceptance Tests from Puppeteer to Playwright](#migrating-acceptance-tests-from-puppeteer-to-playwright) + * [Console errors logging functionality in Acceptance Tests](#console-errors-logging-functionality-in-acceptance-tests) + * [Screenshots testing functionality in Acceptance Tests (Puppeteer)](#screenshots-testing-functionality-in-acceptance-tests-puppeteer) + * [Screenshots testing functionality in Acceptance Tests (Playwright)](#screenshots-testing-functionality-in-acceptance-tests-playwright) + * [Updating Screenshots for Acceptance Tests (Puppeteer)](#updating-screenshots-for-acceptance-tests-puppeteer) +* [Acceptance Tests for Mobile](#acceptance-tests-for-mobile) + * [How to write tests for mobile](#how-to-write-tests-for-mobile) + * [How to run mobile acceptance tests](#how-to-run-mobile-acceptance-tests) +* [Fixing Flakes in Acceptance Tests](#fixing-flakes-in-acceptance-tests) + * [Why flakes are problematic](#why-flakes-are-problematic) + * [Preventing flakes](#preventing-flakes) +* [Fixing Flakes](#fixing-flakes) + * [1. Reproduction](#1-reproduction) + * [2. Diagnosis](#2-diagnosis) + * [3. Fix](#3-fix) + * [4. Open a Pull Request](#4-open-a-pull-request) +* [Reference Links](#reference-links) + +## Introduction Acceptance tests are end-to-end tests that test the complete functionality of the application, and this will help users to catch bugs and regressions before they are released ensuring that the code does what it is supposed to do.