Skip to content

Conversation

JMorado
Copy link
Collaborator

@JMorado JMorado commented Jun 6, 2023

Closes #101

@JMorado JMorado closed this Jun 6, 2023
@JMorado JMorado force-pushed the issue-101-unit-test-001 branch from b909b2f to cf52bdb Compare June 6, 2023 15:51
@JMorado JMorado reopened this Jun 6, 2023
@JMorado JMorado changed the title Issue #101 - Bathymetry tests (unit test 001) Bathymetry tests (unit test 001) Jun 6, 2023
@jdha
Copy link
Collaborator

jdha commented Jul 19, 2023

Hi @JMorado - just wondering if you have time to get this ready for merging? If you need a hand let me know!

@JMorado
Copy link
Collaborator Author

JMorado commented Jul 19, 2023

Hi @jdha,

The unit test test_child_grid_colocated is ready and passes on my local repo.
The issue is that we did several ad hoc changes to the main code to "generalise" it, otherwise it would not run.
Probably, we should take a closer look at those changes to check that they do not break anything else before pushing them to this branch?

I am also happy to go ahead and finish the test_child_grid_rotated test, but I will probably need some help as, as far I remember, I was getting other errors coming from other parts of the code...

I think to have #138 ready would be easier in order to have some unit test examples (I expect that no major changes are required to other parts of the code in these)...Maybe @rdPatmore and I could meet for 15 minutes just to set the refactoring plan and then go ahead with the writing of the tests?

Let me know what are your thoughts on this.

@jdha
Copy link
Collaborator

jdha commented Jul 19, 2023

Hi @jdha,

The unit test test_child_grid_colocated is ready and passes on my local repo. The issue is that we did several ad hoc changes to the main code to "generalise" it, otherwise it would not run. Probably, we should take a closer look at those changes to check that they do not break anything else before pushing them to this branch?

I am also happy to go ahead and finish the test_child_grid_rotated test, but I will probably need some help as, as far I remember, I was getting other errors coming from other parts of the code...

I think to have #138 ready would be easier in order to have some unit test examples (I expect that no major changes are required to other parts of the code in these)...Maybe @rdPatmore and I could meet for 15 minutes just to set the refactoring plan and then go ahead with the writing of the tests?

Let me know what are your thoughts on this.

Happy either way - I just thought I'd mention this after having a conversation with @jpolton. He was thinking of creating a few tests for the tide code and couldn't find the unit test example in the main repo. If #138 is easier, happy to help with that - you could even pop a quick unit test in to make sure the refactoring doesn't alter the Boundary Class when using the benchmark data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unit Test 001
2 participants