LogoLogo
  • OFN Testing Documentation
  • Feature Testing Handbook
    • 1. Background
    • 2. Testing
    • 3. Reporting Feedback
    • 4. Launching the next action
  • Manual Testing Handbook
    • 1. Getting started
    • 2. How to do a sanity check (release testing)?
    • 3. How to do a sanity check in production (after a release)?
    • 4. Test cases
    • 5. Work in Progress
  • Automated Testing Handbook
    • System Specs
    • Automate release testing
    • Some more background
    • (R)Spec Conventions
  • Testers Toolkit
    • Multi-Account Containers
    • Flaky specs
    • Re-running Migrations
    • Enabling Open Street Maps
    • Performance testing with Postman
    • Reverting Database Changes
Powered by GitBook
On this page
  • Instance Managers after deploy-checks
  • Devops after-deploy checks
  • Automatic after-deploy smoke tests

Was this helpful?

  1. Manual Testing Handbook

3. How to do a sanity check in production (after a release)?

This section refers to tests which should be performed after the new version goes live (production tests). These checks are complementary

Previous2. How to do a sanity check (release testing)?Next4. Test cases

Last updated 4 years ago

Was this helpful?

Instance Managers after deploy-checks

This is a 5 min check where we should see if:

1- You can login

2- You can create a product and it appears correctly in the shop as supposed

3- You can checkout

4- You see the order on the order view

Devops after-deploy checks

Check general process from #devops-notifications channel

  • Look at Ansible execution info

  • Check there is no new bug

Check bug trackers

  • Be sure on Bugsnag that existing bugs are not increasing

Check performances

  • Take a look at Datadog dashboards

  • Unsual behaviors:

  • Metrics:

Automatic after-deploy smoke tests

This section is WIP. See also the .

https://app.datadoghq.com/watchdog
https://app.datadoghq.com/dash/integration/1/system-metrics?from_ts=1599106501689&live=true&to_ts=1599120901689
issue on GH