Skip to content

Commit d4639bc

Browse files
committed
definition of performance tests, and subsets of them
1 parent 616ed93 commit d4639bc

File tree

1 file changed

+23
-24
lines changed

1 file changed

+23
-24
lines changed

content/06.quality_criteria.md

Lines changed: 23 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -38,47 +38,46 @@ design analysis or side-effects to external systems.
3838
* **[SvcQC.Fun01.1]** Functional tests SHOULD be checked automatically.
3939
* **[SvcQC.Fun01.2]** Functional tests SHOULD include the public APIs of the **Service**.
4040
* **[SvcQC.Fun01.3]** Functional tests SHOULD include the Web interface of the **Service**.
41+
4142
* **[SvcQC.Fun04]** Functional tests SHOULD be provided by the developers of the inderlying
4243
software. [SQA-QC.Fun04].
4344

44-
### Performace and Stress tests [SvcQC.Per]
45+
### Performace tests [SvcQC.Per]
4546

4647
Performance testing verifies that the software meets the specified performance
4748
requirements and assesses performance characteristics - for instance,
4849
capacity and response time [@url:http://www.swebok.org].
4950

50-
Stress testing exercises software at the maximum design load, as well as beyond it,
51+
Stress or Load testing, exercises software at the maximum design load, as well as beyond it,
5152
with the goal of determining the behavioral limits, and to test defense
52-
mechanisms in critical systems [@url:http://www.swebok.org].
53-
54-
Stress testing is a subset of Performance testing
53+
mechanisms in critical systems [@url:http://www.swebok.org]. *Stress testing is
54+
a subset of Performance testing*
5555
[@url:https://www.geeksforgeeks.org/difference-between-performance-and-stress-testing/].
5656

57+
Scalability testing is test methodology in which an application’s or **Service**
58+
performance is measured in terms of its ability to scale up *and/or* scale out the
59+
number of user requests or other such performance measure attributes, through
60+
an increase in the amount of available resources. The definition
61+
is based on [@url:https://dl.acm.org/doi/10.1145/2737182.2737185].
62+
*Scalability testing is a subset of Performance testing*.
63+
64+
Elasticity testing is adequate to **Services** in cloud resources or infrastructures.
65+
Elasticity is based on how quickly a **Services** in a cloud environment is able to
66+
adapt [@url:https://dl.acm.org/doi/10.1145/2737182.2737185], in response
67+
to variable demand or workload for the software service [@doi:10.1186/s13677-019-0134-y].
68+
*Elasticity testing is a subset of Performance testing*.
69+
5770
* **[SvcQC.Per01]** Performance testing SHOULD be carried out to check the
5871
**Service** performance under varying loads.
72+
5973
* **[SvcQC.Per02]** Stress testing SHOULD be carried out to check the
6074
**Service** to determine the behavioral limits under sudden increased load.
6175

62-
### Scalability tests [SvcQC.Sca]
63-
64-
**TO BE REVIEWED**
65-
66-
Scalability Testing is a non-functional test methodology in which an
67-
application’s performance is measured in terms of its ability to scale
68-
up or scale down the number of user requests or other such performance
69-
measure attributes [@url:https://www.softwaretestinghelp.com/what-is-scalability-testing/].
70-
71-
* **[SvcQC.Sca01]**
72-
73-
### Elasticity tests [SvcQC.Ela]
74-
75-
**TO BE REVIEWED**
76-
77-
Elasticity is the level of autonomous adaptation provided by the
78-
cloud layer in response to variable demand for the software
79-
service [@doi:10.1186/s13677-019-0134-y].
76+
* **[SvcQC.Per03]** Scalability testing MAY be carried out to check the
77+
**Service** hability to scale up *and/or* scale out when its load reach the limits.
8078

81-
* **[SvcQC.Ela01]**
79+
* **[SvcQC.Per04]** Elasticity testing MAY be carried out to check the
80+
**Service** hability to scale out or scale in, depending on its demand or workload.
8281

8382
### Documentation [SvcQC.Doc]
8483

0 commit comments

Comments
 (0)