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.

Sign up for GitHub

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

Bugfix docs python refs #59

Merged
merged 1 commit into from
Feb 15, 2024
Merged

Bugfix docs python refs #59

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -115,8 +115,8 @@ start work on the next release.

## Testing

**Unit and integration tests**. HashStore has a full suite of `pytest` tests in the `tests` subdirectory.
Any new code developed should include a robust set of tests for each public
**Unit and integration tests**. HashStore has a full suite of `JUnit` tests in the `tests`
subdirectory. Any new code developed should include a robust set of tests for each public
method, as well as integration tests from new feature sets. Tests should fully
exercise the feature to ensure that it responds correctly to both good data inputs
and various classes of corrupt or bad data. All tests should pass before submitting a PR
Expand All @@ -130,9 +130,9 @@ for this GitHub Actions status badge and make sure it says "Passing":
Code should be written to professional standards to enable clean, well-documented,
readable, and maintainable software. While there has been significant variability
in the coding styles applied historically, new contributions should strive for
clean code formatting. We generally follow PEP8 guidelines for Python code formatting,
typically enforced through the `black` code formatting package. For Java, we typically
follow the [Google Style](https://raw.githubusercontent.com/google/styleguide/gh-pages/eclipse-java-google-style.xml), enforced through the VS Code formatting extensions.
clean code formatting. For Java, we generally follow the [Google
Style](https://raw.githubusercontent.com/google/styleguide/gh-pages/eclipse-java-google-style.xml),
enforced through the VS Code formatting extensions.

## Contributor license agreement

Expand Down
Loading