You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: website/versioned_docs/version-3.16.0/introduction/usage.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ Chaos experiments can be done anywhere in the DevOps cycle. The extent of chaos
12
12
13
13
## Common Use Cases
14
14
15
-
Typical use cases of Litmus include – failure or chaos testing in CI pipelines, increased chaos testing in staging and production and production environments, Kubernetes upgrades certification, post-upgrade validation of services, and resilience benchmarking, etc.
15
+
Typical use cases of Litmus include – failure or chaos testing in CI pipelines, increased chaos testing in staging and production environments, Kubernetes upgrades certification, post-upgrade validation of services, and resilience benchmarking, etc.
16
16
17
17
-**For Developers:** To run chaos experiments during application development as an extension of unit testing or integration testing.
18
18
-**For CI pipeline builders:** To run chaos as a pipeline stage to find bugs when the application is subjected to fail paths in a pipeline.
0 commit comments