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

Add some proper unit testing #4

Open
Vectorrent opened this issue Aug 28, 2024 · 1 comment
Open

Add some proper unit testing #4

Vectorrent opened this issue Aug 28, 2024 · 1 comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@Vectorrent
Copy link
Contributor

Vectorrent commented Aug 28, 2024

There is functional Jest code that already works, in an extremely limited capacity. To begin, I think we should create tests for each model version - to ensure that no version "breaks" during the course of development.

We can focus on testing individual functions later, after adding some basic model tests.

Part of this is going to involve the addition of a maxSteps argument, such that we can test for maxSteps number of iterations, per model. Today, training is just infinite. I added a basic trainSteps argument, to handle this.

@Vectorrent Vectorrent added enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed labels Aug 28, 2024
@Vectorrent
Copy link
Contributor Author

I setup some extremely basic smoke testing for each model version:
https://github.com/0-5788719150923125/ode/blob/main/tests

This should be easy to extend.

@Vectorrent Vectorrent moved this to In progress in Development Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
Status: In progress
Development

No branches or pull requests

1 participant