Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix failing Quest tests #3725

Open
Rkareko opened this issue Mar 5, 2025 · 2 comments
Open

Fix failing Quest tests #3725

Rkareko opened this issue Mar 5, 2025 · 2 comments
Labels
Technical Debt Any Technical Debt present on the main branch

Comments

@Rkareko
Copy link
Contributor

Rkareko commented Mar 5, 2025

Describe the Issue

The following tests are failing according to this test run

> Task :quest:testOpensrpDebugUnitTest
Done executing: Test runCqlLibraryTestForTestResults(org.smartregister.fhircore.quest.CqlContentTest)

CqlContentTest > runCqlLibraryTestForTestResults FAILED
    org.junit.ComparisonFailure at CqlContentTest.kt:261
Running test: Test runCqlLibraryTestForPqMedication(org.smartregister.fhircore.quest.CqlContentTest)
Done executing: Test runCqlLibraryTestForPqMedication(org.smartregister.fhircore.quest.CqlContentTest)

CqlContentTest > runCqlLibraryTestForPqMedication FAILED
    org.junit.ComparisonFailure at CqlContentTest.kt:261
Running test: Test runCqlLibraryTestForControlTest(org.smartregister.fhircore.quest.CqlContentTest)
Done executing: Test runCqlLibraryTestForControlTest(org.smartregister.fhircore.quest.CqlContentTest)
Running test: Test testGetDataCaptureConfig(org.smartregister.fhircore.quest.QuestApplicationTest)
Done executing: Test testGetDataCaptureConfig(org.smartregister.fhircore.quest.QuestApplicationTest)
Running test: Test testGetWorkManagerConfiguration(org.smartregister.fhircore.quest.QuestApplicationTest)
Done executing: Test testGetWorkManagerConfiguration(org.smartregister.fhircore.quest.QuestApplicationTest)
Running test: Test testSentryMonitoringWhenDsnNotBlank(org.smartregister.fhircore.quest.QuestApplicationTest)
@Rkareko Rkareko added the Technical Debt Any Technical Debt present on the main branch label Mar 5, 2025
@FikriMilano
Copy link
Member

fyi @FikriMilano

@Rkareko Rkareko mentioned this issue Mar 10, 2025
11 tasks
@Rkareko
Copy link
Contributor Author

Rkareko commented Mar 10, 2025

fyi @FikriMilano

@FikriMilano the tests are passing as seen here . This might be a case of flaky tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Technical Debt Any Technical Debt present on the main branch
Projects
None yet
Development

No branches or pull requests

2 participants