Skip to content

Quarterly review of tests - 2025-10 #1018

Description

@github-actions

📦 Quarterly review of tests

  • Schedule a Code Club to go over tests
  • Review the {testdown} reports and check time that it takes to run the tests
  • Review the GitHub actions to determine if any tests are notorious for being buggy
  • Review the code coverage reports to identify missing tests and ensure code coverage is >= 80%
  • Identify bottlenecks or challenges encountered during local test runs
  • Update the minimum version of dependencies and ensure that the tests still pass
  • Update devcontainer.json to include the required dependencies for developers
  • Update the test README.md (WIP in PR refactor(tests): update integration test setup #990)
  • Review the ability to perform the tests as a new developer
  • Triage open issues related to testing
  • Discuss the need for future tests and make an issue that lays out the plan

Notes

call-r-cmd-check workflows are taking longer to complete, increasing from 14 - 35 mins (2e9ddd4) to 22 - 49 mins (b86e9c6), depending on the operating system.

  • The three longest-running tests that may need optimization are:

  • tests/testthat/test-integration-fims-estimation-random-effects-without-wrappers.R (> 19 min)

  • tests/testthat/test-integration-caa-mle-wrappers.R (> 6 min)

  • tests/testthat/test-integration-caa-mle.R (> 8 min)

Using Config/testthat/start-first: file_a, file_b to prioritize certain integration tests doesn’t appear to reduce overall runtime.

  • test-parallel-caa-mle-wrappers.R is outdated and needs to be updated to use the latest wrapper function.

Generated automatically by quarterly-review-of-tests.yml

Metadata

Metadata

Assignees

Labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions