# 测试

### Soak testing

浸泡测试涉及在连续的可用性期内测试具有典型生产负载的系统，以验证生产使用下的系统行为。

如果无法进行此类扩展测试，则可能需要推断结果。例如，如果要求系统在100个小时内处理10,000个事务，则可以在较短的持续时间内（例如50个小时）完成代表实际生产用途（和保守估计）的10,000个事务的处理。良好的浸泡测试还应包括模拟峰值负载而不是平均负载的能力。如果无法在特定时间段内控制负载，则可以选择（保守地）让系统在测试期间以峰值生产负载运行。

* [What is soak testing ?](https://www.katalon.com/resources-center/blog/soak-testing/)
* <https://en.wikipedia.org/wiki/Soak_testing>
* <https://www.guru99.com/soak-testing.html>
  * In Software Engineering, Soak testing is done to determine if the application under test can sustain the continuous load.
  * It is a type of performance test.
  * It helps the system to determine whether it will stand up to a very high volume of usage
  * In this type of testing, what basically monitored is the memory utilization by an application in a system
  * Checks that need to be done by any user/tester before they begin with Soak Testing include
    * Monitor the database resource consumption.
    * Monitor the server resource consumption (ex- CPU usage).
    * Soak test should run with realistic user concurrency.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://shniu.gitbook.io/cs/system-design/ce-shi.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.