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

Improve unit testing #9

Closed
1 of 3 tasks
whitead opened this issue Apr 1, 2019 · 3 comments
Closed
1 of 3 tasks

Improve unit testing #9

whitead opened this issue Apr 1, 2019 · 3 comments
Assignees
Milestone

Comments

@whitead
Copy link
Collaborator

whitead commented Apr 1, 2019

  • Add C++ tests
  • Add coverage analysis
  • Add timing tests for assessing regression in performance
@whitead whitead added this to the 0.2 Release milestone Apr 1, 2019
@whitead
Copy link
Collaborator Author

whitead commented May 13, 2019

Feel free to split this across multiple milestones. Especially the timing tests. You can see examples of tests in hoomd-blue/test

@RainierBarrett RainierBarrett mentioned this issue May 31, 2019
@whitead whitead modified the milestones: 0.2 Release, 0.3 Release Jun 3, 2019
@RainierBarrett
Copy link
Collaborator

We can run pytest --cov=hoomd-tf/htf hoomd-tf/htf/test-py to get code coverage reported, and for timing information, we can run benchmark_xla.py. Despite its name, it can be used to benchmark with and without use of XLA, and records execution timesteps per second in a file when it's finished.

@whitead
Copy link
Collaborator Author

whitead commented Jul 19, 2019

Closing it for now

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

No branches or pull requests

2 participants