Week 2 Demo proposal: Test Prioritization#2709
Merged
sofiabobadilla merged 2 commits intoKTH:2025from Aug 30, 2025
Merged
Conversation
Collaborator
|
Waiting for new version after lab discussion :) |
Author
|
@sofiabobadilla thank you for your feedback! Here is the updated version of the proposal. |
Author
|
@sofiabobadilla we can still get the proposal approved until Monday right (or the deadline of 3 days is only for submitting the proposal)? |
Collaborator
|
HI @AhmadAddee Remember to propose a good narrative, you did very well on the lab already, so just polish the idea. Looking forward to it! Merging 🤠 |
Collaborator
|
@AhmadAddee would you be able to share your presentation? I would like to know which tools in GitHub actions you used. My email is amansha@kth.se. |
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
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
Rule-based automated test execution through CI-pipeline
Names and KTH ID
Deadline
Category
Description
The purpose with this demo is to demonstrate automated test prioritization in a CI-pipeline implemented in the pytest-based testing project.
We will build a simple pytest-based testing project with some test scripts for different purposes. After that, we will implement GitHub-builtin actions to handle the test prioritization - chooses which tests shall be executed based on what has been modified/added to the project. For instance, if a Python file is added, only run Python-quality checks. We will also take a look at tag-based rules and investigate the posibility of setting dependency-based rules.
The tools we're looking at to use are GitHub or GitLab built-in Continouse Integration tools (CI Actions).
The plan of what will be created:
Relevance
This idea matters to DevOps because in real life scenario, it's not realistic to execute all kinds of tests for every push/pull request (because it's time- and resources-demanding), and CI should be effective (be effective by being selective). At the same time, we need to make sure that not-verified code is not merged into production before verification. So, a decisive mechanism is needed to make sure only specific tests are executed for specific purpose.