Главная
Study mode:
on
1
Introduction
2
Overview
3
Netflix
4
Chaos Monkey
5
Amazon Audible
6
Case Engineering
7
Scale it down
8
First situation
9
Second situation
10
Dealing with poor connectivity
11
The idea of chaos testing
12
Example app
13
Add packages
14
Add chaos
15
Triggers
16
Login view model
17
Services being slow
18
Overloads
19
Responsiveness
20
Running Application
21
LockService
22
Changing the data returned
23
Get Customers
24
Transform
25
Demo Time
26
Thoughts on integration
Description:
Discover how to implement in-app chaos testing to uncover potential issues in software development. Learn about the importance of testing scenarios beyond traditional unit and integration tests, such as third-party service failures, slow response times, and resource limitations. Explore real-world examples and techniques for breaking software without altering the codebase. Gain insights into Netflix's Chaos Monkey, Amazon Audible's case engineering, and how to scale down these concepts for smaller applications. Follow along with a practical demonstration of adding chaos to an example app, including implementing triggers, simulating slow services, and testing responsiveness. Understand the value of chaos testing in identifying and addressing potential problems early in the development process, ultimately leading to more robust and reliable software.

How to Do In-App Chaos Testing

NDC Conferences
Add to list