28 lines
1.2 KiB
Markdown
28 lines
1.2 KiB
Markdown
---
|
|
title: Quantitative Testing
|
|
---
|
|
## Quantitative Testing
|
|
|
|
This is a stub. <a href='https://github.com/freecodecamp/guides/tree/master/src/pages/product-design/quantitative-testing/index.md' target='_blank' rel='nofollow'>Help our community expand it</a>.
|
|
|
|
<a href='https://github.com/freecodecamp/guides/blob/master/README.md' target='_blank' rel='nofollow'>This quick style guide will help ensure your pull request gets accepted</a>.
|
|
|
|
Quantitative Testing means testing in order to establish the frequency, magnitude, recurrence of a given hypothesis or phenomenon.
|
|
|
|
In software terms it could many any of the following (but not limited to):
|
|
- Percentage of unique users taking a certain action on your website/interface
|
|
- Number of times your app crashes
|
|
- Mean response time of your server for a specific request by a set number of users
|
|
- Total number of requests your server can handle before the response time begins to degrade
|
|
|
|
As such Quantitative Testing could be performed within any of the following umbrella testing activites:
|
|
### A/B Testing
|
|
### Performance Testing
|
|
### Load Testing
|
|
|
|
|
|
#### More Information:
|
|
<!-- Please add any articles you think might be helpful to read before writing the article -->
|
|
|
|
|