-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Stop R process if AppDriver fails in test-examples
#820
Conversation
test-examples
Code Coverage Summary
Diff against main
Results for commit: 4e9a0b2 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
Unit Tests Summary 1 files 22 suites 12m 47s ⏱️ Results for commit 4e9a0b2. ♻️ This comment has been updated with latest results. |
Unit Test Performance Difference
Additional test case details
Results for commit 1fd2b00 ♻️ This comment has been updated with latest results. |
test-examples
test-examples
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change looks good, I tested ran the test-examples.R file and all test report: "Skip: example-...Rd\nReason: testing depth 3 is below current testing specification 5"
Is this something that could affect end-users? Is it something that could be improved for them?
It doesn't affect any users as all end-to-end/interface testing is behind this "testing depth" It's a testing specific bug, but if it appears it will possibly crash the system. To test out the scenario this PR is fixing you can install teal before the decorator branch is merged and run the tests. This should create a bunch of failed tests and you can check on the process list if there are no lingering R processes renv::install("insightsengineering/teal@161e48056964623c2780c96b13b71c704dcadb1a")
withr::local_envvar("TESTING_DEPTH" = 5)
devtools::test(filter = "examples") |
Pull Request
Fixes insightsengineering/teal.modules.clinical#1302 on
teal.modules.general