Completed table layouts to eradicate some of the linting errors

Author: matthewscauser

docs/acc-reports-training.md

@@ -24,4 +24,4 @@ Practice session on web scanning tools (Wave, Browserstack, Accessible)
 
 Practice session with screen readers
 
-How to scope test plans to achieve WCAG 2.2 (AA) rating
+How to scope test plans to achieve WCAG 2.2 (AA) rating

docs/auto-approved-tools.md

@@ -23,8 +23,8 @@ order: 8
 
 ## Automation Testing Frameworks
 
-| Tool               | Purpose                                       | Reasoning                                                                                                                                                                                                                                                                                                                                 |
-| ------------------ | --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Tool               | Purpose                                       | Reasoning                                                                                                                                                                                                                                                                                                                                 | 
+| ------------------ | --------------------------------------------- |  ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Cypress            | Front‑end UI Functional Automation (Web)      | Pre‑approved for UKHSA QAT. It allows quicker automation and easier test creation for small/moderate complexity scripts. Supports multiple integrations such as CI/CD via ADO Pipelines, Jenkins, Azure Key Vault, JSON, Cucumber, SpecFlow, API testing and TestOps reporting dashboards.                                                |
 | Playwright         | Front‑end UI Functional Automation (Web)      | Pre‑approved for UKHSA QAT. Offers simplified automation with rich features, works across multiple browsers (Chromium, WebKit, Firefox). Supports C#, JS, Python and Java. Integrates with Azure pipelines.                                                                                                                               |
 | Appium             | Mobile Automation Framework                   | Pre‑approved for UKHSA QAT. Supports iOS and Android automation with integration to ADO, SpecFlow and Appium Inspector.                                                                                                                                                                                                                   |
@@ -36,7 +36,7 @@ order: 8
 ## Automation Testing Tools
 
 | S.No | Tool Name       | Test Phase / Process                                      | Purpose                                                                 | License Information |
-| ---- | ---------------- | -----------------------------------------------------------| ----------------------------------------------------------------------- | -------------------- |
+| ---- | ---------------- | ---------------------------------------------------------- | ----------------------------------------------------------------------- | -------------------- |
 | 1    | Visual Studio    | Functional Test Automation                                | IDE for developing automation                                           | Open Source          |
 | 2    | Cucumber         | Automation Framework                                      | Allows Behaviour Driven Development (BDD)                               | Open Source          |
 | 3    | Selenium         | Automation Framework (Web)                                | Browser automation                                                      | Open Source          |
@@ -62,7 +62,7 @@ order: 8
 ## Accessibility Testing
 
 | Tool                                | Purpose                    | Reasoning |
-| ---------------------------------- | -------------------------- | --------- |
+| ----------------------------------- | -------------------------- | --------- |
 | Silktide (Silktide Accessibility Pro version) | WCAG 2.2 verification tool | This tool has been pre-approved by UKHSA ensuring compliance with WCAG 2.2 standards. It offers a holistic means of verifying user-path accessibility. |
 | Wave web accessibility evaluation tool | WCAG 2.2 verification tool | The tool has been pre-approved by UKHSA ensuring compliance with WCAG 2.2 standards. It provides an intuitive region‑level WCAG 2.2 interface. |
 | DigitalA11Y Accessible Web Helper   | Colour Contrast Checker     | User‑centred tool that DigitalA11Y Accessible Web Helper for checking colour contrast on web pages. The software will help testers and developers ensure colour contrast ratios meet accessibility (WCAG 2.2 AA) compliance. |
@@ -77,4 +77,4 @@ order: 8
 | Zoom (built-in Apple Software)           | Screen Magnifier for mobile iOS | The built‑in Zoom feature on Apple devices offers an efficient screen magnification solution that aligns with Apple’s accessibility guidelines. This tool ensures consistent mobile user experience for individuals with visual impairments. |
 | Accessibility Zoom (built‑in Android Software) | Screen Magnifier for mobile Android | Utilising the native Android Accessibility Zoom feature ensures compatibility and user‑centric testing. It aligns with Enterprise Architecture Principles by leveraging Android’s built‑in accessibility tools. |
 | VoiceOver (built‑in Apple Software)      | Speech Recognition Test for mobile iOS | VoiceOver is an iOS native assistive tool which supports screen reading on iOS. Its design aligns with Apple’s commitment to accessibility and enables consistent verification of speech‑based accessibility needs. |
-| Accessibility Speak (built‑in Android Software) | Speech Recognition Test for mobile Android | Accessibility Speak is built‑in Android tool for speech recognition, enhancing user accessibility on Android devices. |
+| Accessibility Speak (built‑in Android Software) | Speech Recognition Test for mobile Android | Accessibility Speak is built‑in Android tool for speech recognition, enhancing user accessibility on Android devices. |

docs/auto-test-design-guide.md

@@ -183,4 +183,4 @@ order: 9
 - Data Sources: Identify and use consistent data sources for testing (e.g., databases, flat files) while ensuring they are applicable across mobile, web, and API tests.
 - Data Security: Ensure test data is anonymised and does not contain sensitive information, adhering to UKHSA data protection policies.
 - Data Consistency: Maintain consistency between the test data used in automated scripts and the data in the AUT.
-- Environment Independence: Test data should be configurable to work across different environments (e.g., development, staging, production).
+- Environment Independence: Test data should be configurable to work across different environments (e.g., development, staging, production).

docs/auto-test-plan-template.md

@@ -24,7 +24,7 @@ It also covers:
 ## Version History
 
 | Version | Date       | Author        | Description                                       |
-|---------|------------|----------------|---------------------------------------------------|
+| ------- | ---------- | -------------- | ------------------------------------------------- |
 | 0.1     | <dd/mm/yyyy> | <Full Name>   | Draft Document for review and feedback            |
 | 0.2     | <dd/mm/yyyy> | <Full Name>   | Feedback Incorporated                             |
 | 1.0     | <dd/mm/yyyy> | <Full Name>   | Final Version for Approval / Sign‑off             |
@@ -34,7 +34,7 @@ It also covers:
 ## Document Review
 
 | Name           | Role                    | Responsibility | Version | Date         |
-|----------------|--------------------------|----------------|---------|--------------|
+| -------------- | ------------------------ | -------------- | ------- | ------------ |
 | <Full Name>    | Agile Delivery Manager   | Sign‑off       | <v>     | <dd/mm/yyyy> |
 | <Full Name>    | Product Owner            | Reviewer       | <v>     | <dd/mm/yyyy> |
 | <Full Name>    | Test Lead                | Reviewer       | <v>     | <dd/mm/yyyy> |
@@ -123,7 +123,7 @@ The framework will also use recommended automation patterns:
 Below is a list of the types of functional automation tests executed using “tags” in the framework.
 
 | Functional Test Type | Description |
-|----------------------|-------------|
+| -------------------- | ----------- |
 | **Smoke Tests**      | Basic checks to ensure app is up |
 | **Regression**       | Verify no new code breaks existing features |
 | **E2E**              | End‑to‑end business flow validations including integration tests |
@@ -173,7 +173,7 @@ Below is a list of the types of functional automation tests executed using “ta
 Automation test delivery can only start after completion of the below:
 
 | Entry Criteria | Responsible |
-|----------------|-------------|
+| -------------- | ----------- |
 | Reviewed & finalised App/Service details, application URLs, cloud account access etc. | Project Development Team |
 | User Access Created, Permissions Granted, Test Interface Credentials | DevOps/Project Team |
 | Test Environment Ready (SIT/UAT environment ready to use) | Automation Tester with support from DevOps/Service Desk |
@@ -187,7 +187,7 @@ Automation test delivery can only start after completion of the below:
 ## Exit Criteria
 
 | Exit Criteria                                                                 | Responsible                                  |
-|--------------------------------------------------------------------------------|-----------------------------------------------|
+| ------------------------------------------------------------------------------ | --------------------------------------------- |
 | All tests automated and executed which are in the scope of the delivery        | Automation Tester                             |
 | All automation open defects should be closed/mitigated or downgraded           | Automation Tester                             |
 | The automation regression tests are integrated in the CI/CD application deployment pipelines at test environment | Automation Tester, Project Dev Team and DevOps |
@@ -208,7 +208,7 @@ Automation test delivery can only start after completion of the below:
 > *Add/Remove relevant automation risks which impact the project deliverables. The below examples are not exhaustive—add & remove as needed.*
 
 | Risk                                             | Risk Severity | Risk Owner                    | Risk Status           |
-|--------------------------------------------------|--------------|------------------------------|------------------------|
+| ------------------------------------------------ | ------------ | ---------------------------- | ---------------------- |
 | Automation tools blocked                         | High / Medium / Low | Automation Tester / Test Lead / Automation Manager | Open / Mitigated / Closed |
 | Incomplete automation coverage                   | High / Medium / Low | Automation Tester            | Open / Mitigated / Closed |
 
@@ -235,7 +235,7 @@ See: **UKHSA Approved Tools and Automation Guidelines**
 ## Tools (examples only — replace with live tool options)
 
 | Tool               | Purpose                                 |
-|--------------------|-------------------------------------------|
+| ------------------ | ----------------------------------------- |
 | Playwright         | Browser automation                        |
 | Cypress            | Browser automation                        |
 | Selenium / WebDriver (UI) | UI automation                      |
@@ -251,7 +251,7 @@ See: **UKHSA Approved Tools and Automation Guidelines**
 Below are the key automation milestones to be tracked as part of the project.
 
 | Milestone             | Deliverable                 | Owner              | Schedule         |
-|-----------------------|------------------------------|---------------------|------------------|
+| --------------------- | ---------------------------- | ------------------- | ---------------- |
 | Framework Setup       | Automation framework setup   | QA Team             | [Date Range]     |
 | Scripting Development | Automated test scripts       | Automation Tester   | [Date Range]     |
 | Test Data Management  | Test data created            | QA/Dev Team         | [Date Range]     |
@@ -264,7 +264,7 @@ Below are the key automation milestones to be tracked as part of the project.
 # 8. Resource, Roles & Responsibilities — Key Programme Resource
 
 | Role                      | When Required | RACI | Key Responsibilities |
-|---------------------------|--------------|------|-----------------------|
+| ------------------------- | ------------ | ---- | --------------------- |
 | Agile/Test Delivery Manager | All phases | R/A | Ensure tooling & automation are aligned, sign‑off stages, oversee delivery. |
 | Test Lead / QA Manager     | All phases | R/C | Create test approach; manage test execution; coordinate across teams. |
 | QAT Test Automation Lead   | All phases | R/C | Define automation strategy; support automation activities; ensure standards followed. |
@@ -326,9 +326,9 @@ BAU handover includes:
 Example list below — expand as needed for the project.*
 
 | Abbreviation | Description                                      |
-|--------------|--------------------------------------------------|
+| ------------ | ------------------------------------------------ |
 | QAT          | Quality Assurance Testing                        |
 | Automation   | Software Functional Test Automation              |
 | CI/CD        | Continuous Integration and Continuous Delivery   |
 
----
+---

docs/func-test-guides-reqs.md

@@ -103,4 +103,3 @@ For sample templates related to the deliverables mentioned above, please refer t
       • Defect closure report
    • Risks and Issues
    • Recommendations
-``