Skip to content

refactor: Reorganise constitutive tests #3581

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

Draft
wants to merge 11 commits into
base: develop
Choose a base branch
from

Conversation

dkachuma
Copy link
Contributor

@dkachuma dkachuma commented Mar 4, 2025

The directory src/coreComponents/unitTests/constitutiveTests is getting clattered with constitutive driver based tests. This PR moves all the driver based test xmls into a sub-directory driverTests and all their baselines to baselines. The idea is to keep src/coreComponents/unitTests/constitutiveTests for the actual c++ tests.

@dkachuma dkachuma added the type: cleanup / refactor Non-functional change (NFC) label Mar 4, 2025
@dkachuma dkachuma self-assigned this Mar 4, 2025
@dkachuma dkachuma changed the title Reorganise constitutive tests cleanup: Reorganise constitutive tests Mar 4, 2025
@dkachuma dkachuma added the ci: run integrated tests Allows to run the integrated tests in GEOS CI label Mar 4, 2025
@dkachuma dkachuma marked this pull request as ready for review March 4, 2025 18:15
@dkachuma dkachuma changed the title cleanup: Reorganise constitutive tests refactor: Reorganise constitutive tests Mar 4, 2025
@CusiniM
Copy link
Collaborator

CusiniM commented Mar 6, 2025

I think it would be better to make the drivers standalone executables and transform these tests into integratedTests.

@dkachuma dkachuma requested a review from MelReyCG as a code owner March 11, 2025 15:30
@dkachuma
Copy link
Contributor Author

dkachuma commented Mar 11, 2025

I think it would be better to make the drivers standalone executables and transform these tests into integratedTests.

These tests are complete geos input files that can be run directly with the geosx executable. However I am having trouble adding them as integratedTests because there is no restart or time history - these don't really make sense for these tests. @CusiniM Can you please advise how I can add an integrated test without a restart check or a curve check.

@dkachuma dkachuma marked this pull request as draft March 18, 2025 14:23
Returns:
geos.hdf5_wrapper: The hdf5 wrapper for the data
"""

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are you doing this so that you can then use a curve_check ? This is good for now. In the future we may want to simply output an hdf5 directly from the constitutiveDriver.

@@ -53,24 +53,4 @@
</Events>

<!-- SPHINX_PVTDRIVER_EVENTS_END -->
<!-- Mesh is not used, but GEOSX throws an error without one. Will resolve soon-->
<Mesh>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

were you able to resolver the need for the mesh? I don't see it in this PR but if that's the case, it's great!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci: run integrated tests Allows to run the integrated tests in GEOS CI flag: ready for review type: cleanup / refactor Non-functional change (NFC)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants