Week 2 demo: Automatic network failure resilience testing - #2992
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Assignment Proposal
Title
Automatic network failure resilience testing
Names and KTH ID
Deadline
Category
Description
We will implement and demo network failure testing within a CI pipeline.
First we will create a basic app for blogging, which will be connected to an external database (PostgreSQL). The CI pipeline (automated tests using Github actions set to run tests on PUSH/PR) has two targets: One without resilience testing, and one with. The first target/job would pass PRs under normal conditions, since there is nothing inherently wrong with the code (and no latency etc., causing issues). Then, in the second target, we deliberately introduce latency and timeouts of variyng degree using Toxiproxy (https://github.com/shopify/toxiproxy). The point is to see that our integration tests catch lacking network error handling, and therefore denies the PR (marks it as having failed tests). After that we add some resilience to the application, i.e. timeout and retry handling and show that the tests then pass.
Relevance
When working with real world networking applications, problems will inevitabily occur with connection or external services. It is then crucial to test for these scenarios, and that the software can handle the issues that occur without breaking the rest of the program to ensure that it is resilient. This is relevant to DevOps since we test the resilience during CI, instead of discovering the issues after deploying to a real world scenario.