> For the complete documentation index, see [llms.txt](https://ofn-user-guide.gitbook.io/ofn-testing-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ofn-user-guide.gitbook.io/ofn-testing-handbook/testing-handbook-v2-from-google-drive/how-to-do-a-sanity-check-in-production-after-a-release.md).

# 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

## Instance Managers after deploy-checks

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

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: <https://app.datadoghq.com/watchdog>
* Metrics: <https://app.datadoghq.com/dash/integration/1/system-metrics?from_ts=1599106501689&live=true&to_ts=1599120901689>

## Automatic after-deploy smoke tests

This section is WIP. See also the [issue on GH](https://github.com/openfoodfoundation/ofn-install/issues/493).