feat: use local db for integration tests #1488

LucasSantos27 · 2025-09-15T14:28:58Z

This PR introduces improvements to the integration testing workflow by moving from a remote database dependency to a fully local setup. The main updates include:

Added a new docker-compose setup and management commands to run tests using a local PostgreSQL instance instead of relying on remote services.
Implemented factory-based mocks and seeding commands to simplify the creation of test data across Checkouts, Builds, Tests, Issues, and Incidents.
Updated the CICD to adopt the local database approach.
Added a guideline on how to run integration tests locally, including setup and usage instructions.

Note: Please check the new documentation to better understand the changes and make the review process easier.

Related issue

Closes Use local DB for CI tests #1397

MarceloRobert · 2025-09-16T13:06:04Z

backend/kernelCI_app/tests/factories/checkout_factory.py

+                [
+                    "maestro",
+                    "redhat",
+                    "microsoft",
+                    "broonie",
+                    "linaro",
+                    "0dayci",
+                    "syzbot",
+                    "android-mainline",
+                    "next-pending-fixes",
+                ]


Feels a bit weird that you are mixing origin names with tree names. Is this variable supposed to store realistic origins or just any value?

any value for "fake checkouts", so I'll change to fake-origin

MarceloRobert · 2025-09-16T13:12:23Z

backend/kernelCI_app/management/commands/seed_test_data.py

+        )
+        builds.append(failed_build)
+
+        [uncategorized_issues] = [i for i in issues if i.id == "Uncategorized"]


Uncategorized tests are (ironically) a category that we created just for tests that failed but had no incidents related to them, there are no issues called "Uncategorized". In other words, if a test fails but has no incidents related to it, then that test is uncategorized.

MarceloRobert · 2025-09-16T13:45:15Z

backend/kernelCI_app/tests/factories/build_factory.py

+                "5b4ec6e1eb7603b6d86a172d77efdf75eb741e7e",  # ALLWINNER_HARDWARE
+                "0704a15b930cf97073ce091a0cd7ad32f2304329",  # ALLWINNER_HARDWARE
+            ]
+            else random.choice(


Add the possibility for null status as well please

I've already changed this part, so I'm not sure which part to change, sorry. Would it be the status?

MarceloRobert · 2025-09-16T13:51:29Z

backend/kernelCI_app/tests/factories/issue_factory.py

+                "maestro:e602fca280d85d8e603f7c0aff68363bb0cd7993",
+                "broonie:bb2eb9603973cb353faa8e780b304d3537220228",
+                "linaro:30MeoIqiN9rKm6s2lQLaThEnGHF",
+                "Uncategorized",


ditto no Uncategorized issues

MarceloRobert · 2025-09-16T13:51:53Z

backend/kernelCI_app/tests/factories/issue_factory.py

+            "linaro",
+            "0dayci",
+            "syzbot",
+            "android-mainline",


ditto origins + treeName

MarceloRobert · 2025-09-16T13:56:45Z

backend/kernelCI_app/tests/factories/test_factory.py

+            else BuildFactory()
+        )
+    )
+    origin = factory.LazyAttribute(lambda obj: obj.build.origin)


I'd suggest adding the possibility of a test having an origin that's different from the build's origin, this is something that is already happening

It can be changed in the future, but for now we can follow the same origin of build.

MarceloRobert · 2025-09-16T13:58:07Z

backend/kernelCI_app/tests/factories/test_factory.py

+        }
+    )
+
+    status = factory.LazyAttribute(


feels like a lot of hardcoded strings, maybe move them to variables?

MarceloRobert · 2025-09-16T14:00:13Z

backend/scripts/run_locally_integration_tests.sh

do you need to use docker-compose instead of docker compose? I believe the second one is the newer format

I'll remove this part, it's just to test if you'd like

MarceloRobert · 2025-09-16T14:00:24Z

backend/scripts/run_locally_integration_tests_full.sh

ditto docker-compose / docker compose

- Create a backend and db services in new docker-compose to run integration tests with local db. part of #1397

it will be useful for integration tests with local db part of #1397

this command change the django setting modules to `test_settings` which uses a local postgresql database part of #1397

- Use factories with factory boy to create mocks for all tables in local DB tests: - Checkout - Build - Test - Issues - Incidents `test_data_mapping` is used to map the data from Trees, Builds, Tests, Issues and Incidents to the factories. part of #1397

- Issues and Checkout can be changed - Build, Test and Incident are created from Checkout and Issues part of #1397

we will use a local postgresql database for integration tests instead of a remote one. We must set up the database before running the tests. With this change, we avoid problems with network issues and changes in the remote database. part of #1397

- Explain the purpose of integration tests - Provide setup instructions for local database part of #1397

MarceloRobert · 2025-09-19T17:44:03Z

backend/kernelCI_app/management/commands/seed_test_data.py

+        Incidents.objects.all().delete()
+        Issues.objects.all().delete()
+        Tests.objects.all().delete()
+        Builds.objects.all().delete()
+        Checkouts.objects.all().delete()


I feel like there should be some guardrails here... We don't want to accidentally delete everything in production db

LucasSantos27 force-pushed the integration-tests-using-local-db branch from 92d9af2 to b0c5f9f Compare September 15, 2025 14:30

MarceloRobert assigned LucasSantos27 Sep 15, 2025

MarceloRobert reviewed Sep 16, 2025

View reviewed changes

LucasSantos27 force-pushed the integration-tests-using-local-db branch from f3fa8d0 to 6ab213b Compare September 17, 2025 19:09

LucasSantos27 added 3 commits September 18, 2025 08:26

chore: add new docker-compose file for tests with local db

51c3375

- Create a backend and db services in new docker-compose to run integration tests with local db. part of #1397

chore: add factory boy for test data generation

d8effe6

it will be useful for integration tests with local db part of #1397

chore: add use-local-db command for integration tests

fa179f1

this command change the django setting modules to `test_settings` which uses a local postgresql database part of #1397

LucasSantos27 force-pushed the integration-tests-using-local-db branch from 6ab213b to 7470b23 Compare September 18, 2025 11:32

LucasSantos27 added 3 commits September 18, 2025 11:00

test: create a management command to seed test data in local DB

bfef231

- Issues and Checkout can be changed - Build, Test and Incident are created from Checkout and Issues part of #1397

LucasSantos27 force-pushed the integration-tests-using-local-db branch from 7470b23 to 7787bcd Compare September 18, 2025 14:02

LucasSantos27 changed the title ~~WIP: Integration tests using local db~~ feat: use local db for integration tests Sep 18, 2025

LucasSantos27 marked this pull request as ready for review September 18, 2025 14:04

LucasSantos27 force-pushed the integration-tests-using-local-db branch from 7787bcd to a1684a2 Compare September 18, 2025 14:17

LucasSantos27 requested a review from MarceloRobert September 18, 2025 14:53

docs: add new documentation for integration tests

7978d6a

- Explain the purpose of integration tests - Provide setup instructions for local database part of #1397

LucasSantos27 force-pushed the integration-tests-using-local-db branch from a1684a2 to 7978d6a Compare September 19, 2025 13:41

MarceloRobert reviewed Sep 19, 2025

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat: use local db for integration tests #1488

feat: use local db for integration tests #1488

LucasSantos27 commented Sep 15, 2025 •

edited

Loading

Uh oh!

MarceloRobert Sep 16, 2025

Uh oh!

LucasSantos27 Sep 17, 2025

Uh oh!

MarceloRobert Sep 16, 2025

Uh oh!

MarceloRobert Sep 16, 2025

Uh oh!

LucasSantos27 Sep 17, 2025

Uh oh!

MarceloRobert Sep 16, 2025

Uh oh!

MarceloRobert Sep 16, 2025

Uh oh!

MarceloRobert Sep 16, 2025

Uh oh!

LucasSantos27 Sep 17, 2025

Uh oh!

MarceloRobert Sep 16, 2025

Uh oh!

MarceloRobert Sep 16, 2025

Uh oh!

LucasSantos27 Sep 17, 2025

Uh oh!

MarceloRobert Sep 16, 2025

Uh oh!

LucasSantos27 Sep 17, 2025

Uh oh!

MarceloRobert Sep 19, 2025

Uh oh!

Uh oh!

feat: use local db for integration tests #1488

Are you sure you want to change the base?

feat: use local db for integration tests #1488

Conversation

LucasSantos27 commented Sep 15, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Related issue

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

LucasSantos27 commented Sep 15, 2025 •

edited

Loading