This is a stub. <ahref='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>.
<ahref='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 (or alternatively A/B/n Testing where several variations are involved) involves multiple variations of the same web page being presented to users with the aim of ascertaining which variant is more effective.
Performance Testing is, as its name might suggest, the process of evaluating how a site performs under various conditions; with the aim of determining responsiveness, stability and the extent to which it satisfies any stipulated prerequisites.
Load Testing is the process of subjecting a site (or server, application etc.) to simulated 'real-life' conditions, wherein multiple users (dozens, hundreds, thousands, millions etc.) access it at once. This is done with the aim of determining how it will perform under various levels of demand. Load Testing might be considered a variant of Performance Testing.
