Demo Proposal: CI Pipeline with Integration Testing Against a Real Database - #2977
Merged
Conversation
Updated the README to reflect team members and clarified the
algomaster99
approved these changes
Sep 3, 2026
algomaster99
left a comment
algomaster99
left a comment
Collaborator
There was a problem hiding this comment.
Great proposal! Looking forward to the demo.
| We will focus on why multiple levels of testing are essential and why unit tests may not be enough. | ||
| Unit tests typically run against mocked or simulated data, so they can pass even when the underlying logic has a | ||
| flaw that only appears when interacting with real data or real databases' behaviour, such as constraints, data types, or case-sensitivity, | ||
| that a mock won't enforce. Code can look fine in isolation but fail when interacting with other components. |
Collaborator
There was a problem hiding this comment.
I like this idea. Would love to see emphasis on shortcomings in the mock testing.
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
CI Pipeline with Integration Testing Against a Real Database
Names and KTH ID
Deadline
Week 2
Category
Demo
Description
The demo will demonstrate a basic CI pipeline with two levels of tests: integration tests alongside unit tests.
We will build a simple shopping list app backed up by a MySQL database as an external service.
The CI pipeline (GitHub Actions) will run on every push/PR.
We will focus on why multiple levels of testing are essential and why unit tests may not be enough.
Unit tests typically run against mocked or simulated data, so they can pass even when the underlying logic has a
flaw that only appears when interacting with real data or real databases' behaviour, such as constraints, data types, or case-sensitivity,
that a mock won't enforce. Code can look fine in isolation but fail when interacting with other components.
Relevance
Continuous Integration is a core DevOps practice: automatically testing every change catches problems early, before they reach production.
Running multiple levels of tests matters because some bugs won't surface until the code interacts with external services.