Skip to content
This repository has been archived by the owner on Dec 20, 2023. It is now read-only.

[Meta Issue] Write tests for codebase #1

Open
7 of 11 tasks
tylerpotts opened this issue Aug 18, 2022 · 2 comments
Open
7 of 11 tasks

[Meta Issue] Write tests for codebase #1

tylerpotts opened this issue Aug 18, 2022 · 2 comments

Comments

@tylerpotts
Copy link
Contributor

tylerpotts commented Aug 18, 2022

Summary

All functions need tests to ensure they do what we expect and to catch bugs before they get into the main branch. The tests should cover all known cases and potential bugs. If new bugs appear, new tests should be written to cover the new bug.

We should generally follow the suggested rules of testing given here:
https://docs.python-guide.org/writing/tests/

This issue covers everything except cli.py, which we will work on next.

Proposed implementation

  • This is a meta issue (aka Epic), so a new issue should be opened for each task. Some tasks are in the list below, but other tasks can be added to this meta issue by editing this description.
  • There are data files in the tests directory that can be used in the tests. Do not modify the data files.
  • All tests should be in the tests directory.
  • Each module in the repo will have a test file named tests_{module name}.py
  • Each test will be a function named test_{some function}.py

Acceptance Criteria

  • All functions and methods (except in cli.py) have tests (full coverage)

Tasks to complete

Tests should be written for each function:

Related to

@kcpevey
Copy link
Collaborator

kcpevey commented Sep 22, 2022

Check here for coverage

1 similar comment
@kcpevey
Copy link
Collaborator

kcpevey commented Sep 22, 2022

Check here for coverage

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

No branches or pull requests

3 participants