Testing
Enzo-E currently uses two different testing frameworks for its test suite,
ctest and pytest. Both frameworks are run on
all pull requests and each has its advantages. You are welcome to use either
when creating new tests. The ctest framework is used primarily for unit
tests (i.e., tests that run from self-contained binaries), but can also be
used for tests that run the enzo-e binary. The pytest framework is
mainly useful for answer tests, where results from two versions of an
enzo-e simulation are compared.
- The ctest Framework
- How to create a new ctest test
- The pytest Framework
- Existing ctest Tests
- Existing Test Simulations
- Accretion Tests
- Adapt Tests
- Balance Tests
- BB Test
- Boundary Condition Tests
- Checkpoint Tests
- Collapse Tests
- Cosmology Tests
- FluxCorrect tests
- Grackle Tests
- Gravity Tests
- Heat Tests
- HelloWorld
- Hierarchy Tests
- Hydro tests
- Initial MUSIC Tests
- Isolated Galaxy Tests
- Merge Sinks Tests
- Methods Tests
- Output Tests
- Parse Tests
- Particle Tests
- Performance Tests
- PPM tests
- PPML Tests
- Sedov Tests
- Shu Collapse Test
- VLCT Tests
- Other Tests
- bb_unigrid_SF_FB
- method_feedback
- test_collapse-bcg2
- test_collapse-bcg3
- test_collapse-dd2
- test_collapse-dd3
- test_collapse-gas-bcg2
- test_collapse-gas-dd2
- test_collapse-gas-hg2
- test_collapse-hg2
- test_collapse-hg3
- test_cosmo-bcg-fc0
- test_cosmo-bcg-fc1
- test_cosmo-bcg
- test_cosmo-cg-fc0
- test_cosmo-cg-fc1
- test_cosmo-cg
- test_cosmo-dd-fc0
- test_cosmo-dd-fc1
- test_cosmo-dd
- test_cosmo-hg-fc0
- test_cosmo-hg-fc1
- test_cosmo-hg
- test_cosmo-mg-fc0
- test_cosmo-mg-fc1
- test_cosmo-mg
- test-flux2-xm
- test-flux2-xp
- test-flux2-ym
- test-flux2-yp
- test-flux3-xm
- test-flux3-xp
- test-flux3-ym
- test-flux3-yp
- test-flux3-zm
- test-flux3-zp
- Existing Answer Tests