Upgrade unit tests to use lightweight case load where possible

[ansjsia]

To speed up solver mode unit tests, tests that don't require loading the mesh have been set to call root.file.read with the parameter lightweight_setup=True.

[raph-luc]

Running solvermode tests here: https://github.com/ansys/pyfluent/actions/runs/7146060041

If any tests fail we can compare with others to see if they were already failing, or if they are new failures: https://github.com/ansys/pyfluent/actions/workflows/weekly-solvermode-test-run.yml

[ansjsia]

Running solvermode tests here: https://github.com/ansys/pyfluent/actions/runs/7146060041

If any tests fail we can compare with others to see if they were already failing, or if they are new failures: https://github.com/ansys/pyfluent/actions/workflows/weekly-solvermode-test-run.yml

@raph-luc I'm noticing these solver mode tests are being run with 24.2 rather than 24.1. 2 of the 4 test failures are caused by changes in API object names (test_boundaries.py::test_boundaries_elbow and test_species_model.py::test_change_create_mixture). Should we delay updating them until 24.1 is released?

test_boundaries.py::test_boundaries_periodic is throwing an AssertionError when comparing two dictionaries. I'll have to do some digging to see if this is caused by an API change.

Would you have any idea on how to investigate test_general.py::test_solver_import_mixingelbow throwing an _InactiveRpcError?

[seanpearsonuk]

Running solvermode tests here: https://github.com/ansys/pyfluent/actions/runs/7146060041
If any tests fail we can compare with others to see if they were already failing, or if they are new failures: https://github.com/ansys/pyfluent/actions/workflows/weekly-solvermode-test-run.yml

@raph-luc I'm noticing these solver mode tests are being run with 24.2 rather than 24.1. 2 of the 4 test failures are caused by changes in API object names (test_boundaries.py::test_boundaries_elbow and test_species_model.py::test_change_create_mixture). Should we delay updating them until 24.1 is released?

test_boundaries.py::test_boundaries_periodic is throwing an AssertionError when comparing two dictionaries. I'll have to do some digging to see if this is caused by an API change.

Would you have any idea on how to investigate test_general.py::test_solver_import_mixingelbow throwing an _InactiveRpcError?

@ansjsia @raph-luc
I believe that we should test against stable APIs here, so yes, we should avoid touching 24.2 at the present time.

[raph-luc]

@ansjsia when comparing the test results from this branch with those from main, we can see that the test failures from this branch are not due to the changes here: these tests were already failing before with the exact same errors. We shouldn't address those in this PR.