# Superior Testing: Managing Production

DevFeed: [Superior Testing: Managing Production](<https://devfeed.tech/articles/superior-testing-managing-production-29378.md>)

Original publisher: [Read original article](<https://arturdryomov.dev/posts/superior-testing-managing-production/>)

Author: Artur Dryomov

Published: 2019-07-30T00:00:00Z

Content type: article

Language: en

Sources: [Artur Dryomov](<https://devfeed.tech/sources/artur-dryomov.md>)

Topics: [Testing](<https://devfeed.tech/topics/testing.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [logging](<https://devfeed.tech/tags/logging.md>), [logs](<https://devfeed.tech/tags/logs.md>), [memory-leaks](<https://devfeed.tech/tags/memory-leaks.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [production](<https://devfeed.tech/tags/production.md>), [testing](<https://devfeed.tech/tags/testing.md>)

## AI overview

This article argues that testing continues in production after deployment, where running the application exposes behavior that controlled environments cannot fully check. It presents monitoring, business and technical analytics, metrics such as memory and thread usage, error rates, and structured logging as ways to understand production behavior and detect issues.

## Source excerpt

The testing process does not magically stop after deploying an artifact. We've only just begun. It is impossible to check everything in a sandboxed environment. From a certain perspective it seems like the whole run time is the testing process. How is it possible to check the correctness without tests? Right -- by running the thing. We do the same in production -- just on a bigger scale and with bigger risks.