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

Testing Master Plan #48

Open
21 of 48 tasks
efaulhaber opened this issue Jan 10, 2023 · 2 comments
Open
21 of 48 tasks

Testing Master Plan #48

efaulhaber opened this issue Jan 10, 2023 · 2 comments
Labels
testing Improvements or additions to tests

Comments

@efaulhaber
Copy link
Member

efaulhaber commented Jan 10, 2023

This is a to-do list for testing and to keep track of the tests we already have.

  • General unit tests
  • Unit tests for WCSPH RHS
  • Unit tests for boundary system RHS
    • Monaghan-Kajtar kernel
    • Monaghan-Kajtar pressure_acceleration
    • Dummy particles pressure_acceleration (RHS tests for dummy particles #327)
    • Adami pressure extrapolation
    • interact!
  • Unit tests for EDAC RHS
    • pressure_evolution
    • interact!
  • Unit tests for solid dynamics
    • Penalty force
    • Correction matrix
    • Deformation gradient and stress tensor
  • Unit tests for neighborhood search
    • TrivialNeighborhoodSearch
    • GridNeighborhoodSearch
      • Basic 2D
      • Basic 3D
      • Periodicity 2D
      • Periodicity 3D
  • Linear interpolation
  • Tests for visualization
  • Tests for callbacks
  • Example tests
    • Simple smoke tests as system tests (Add system tests (smoke tests for now) #47)
    • Add some kind of solution verification for system tests. At least to catch obvious problems like when the solid in FSI is not moving.
    • Properly verify examples that are reproducing papers against the papers.
    • Run example tests with coverage (expensive). We have to track this coverage separately from the unit test coverage, or the unit test coverage report is useless. We may want to think about showing only the unit test coverage badge, or both if possible. Otherwise, the example coverage should just be used internally to keep track of the example tests.
    • Try to test the full feature set with system tests (run examples with different BCs, with and without NHS, with and without viscosity, etc.)
  • Add coverage for unit tests (Enable coverage in CI for unit and integration tests #72)
  • Doctests
  • Run CI on LTS and current stable release versions of Julia (expensive).
@efaulhaber efaulhaber added the testing Improvements or additions to tests label Jan 10, 2023
@svchb
Copy link
Collaborator

svchb commented Nov 1, 2023

@efaulhaber please update

@efaulhaber
Copy link
Member Author

I've updated the list and made it very detailed, so that we have a good overview of what we already have and which tests we still need, exactly. For example, in case we add interact! tests first, we might forget about isolated pressure_acceleration tests, since pressure_acceleration will show up as covered in the coverage report.

Feel free to add any other tests that we want to have, so that we don't forget about them.

CC: @LasNikas

@efaulhaber efaulhaber changed the title Improve testing Testing Master Plan Nov 20, 2023
@efaulhaber efaulhaber pinned this issue Nov 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
testing Improvements or additions to tests
Projects
None yet
Development

No branches or pull requests

2 participants