Skip to content

Latest commit

 

History

History
120 lines (74 loc) · 3.23 KB

test-approach.md

File metadata and controls

120 lines (74 loc) · 3.23 KB
Raw

Test Approach

Quality Gates diagram

These are the quality assurance steps that code changes go through to ensure that they are correct.

flowchart TB

  subgraph before[Before code]
    before1[Definition of Ready]
    before2[Threat Modelling]
  end

  before-->local

  subgraph local[Local development]
    local1[Pair programming]
    local2[Local linting tools]
    local3[Live unit tests]
  end

  local-->remote

  subgraph remote[Push to remote branch]
    remote1[Unit tests run]
    remote2[Mutation tests run]
    remote4[Sonarcloud]
  end

  remote-->pr

  pr(Create Pull Request)

  pr-->dev
  pr-->review

  review{Peer code review}
  
  subgraph dev[Development environment]
    dev1[Automated UI tests]
  end

  dev-->testenvapproval
  
  testenvapproval(Approval to deploy to Test env)

  testenvapproval-->test

  subgraph test[Test environment]
    manual1[Manual exploratory tests]
    manual2[Manual accessibility tests]
    manual3[Manual cross browser tests]
  end

  test-->merge
  review-->merge

  merge(Merge to main)

  merge-->dod

  dod(Definition of Done)

  dod-->prod

  subgraph prod[Production environment]
    prod1[Manual smoke test]
  end

  prod-->adhoc

  subgraph adhoc[Adhoc]
    adhoc1[Accessibility audit]
    adhoc2[Security audit]
    adhoc3[User acceptance]
  end
Loading

Details

Accessibility testing

Automated - create/modify a Cypress-axe accessibilty test. Axe will only test the current state of the elements on the screen so make sure different visual states (e.g. expanded/collapsed, hover) are explicitly set and tested.

Manual - use the Accessibility Insights for Web Chrome extension and follow the assessment guide.

Cross browser testing

Our application is designed to support Microsoft Edge and Google Chrome laptop/PC users.

Automated - there are no automated cross browser tests.

Manual - exploratory testing on Google Chrome and Microsoft Edge to ensure there are no visual differences between browsers.

Exploratory testing

This testing is performed as required after a significant UI change. Results are recorded against the relevant "exploratory test" task in DevOps.

Exploratory testing should use the testers experience with the product to direct their testing of the syste]m/s.

A test charter should be used to bring structure to this testing including an entry and exit criteria, areas under test, bug recording and relevant test date.

Functional testing

Unit

All .NET code is unit tested where possible. Where it is deemed not possible to unit test, code should be marked as excluded from code coverage. .NET unit test quality is measured by mutation testing tool Stryker.NET - a mutation score of at least 80% is required before merging to main.

UI

UI tests verify that the UI behaves as it should under both happy and unhappy path conditions. These tests are are run in an isolated environment with external dependencies (such as APIs and databases) mocked.

Security testing

Audit

As required, specialist security audits will be carried out against the service.