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 additional utility functions and second core function, then write tests #3

Open
drkennetz opened this issue Sep 9, 2020 · 2 comments
Labels
enhancement New feature or request hacktoberfest issues good for hacktoberfest

Comments

@drkennetz
Copy link
Collaborator

For people learning, write additional utility functions, add a second core function, and write tests.

@rjbeers rjbeers added the enhancement New feature or request label Oct 3, 2020
@drkennetz
Copy link
Collaborator Author

There are multiple ways to handle this. We could either create separate branches for more in depth tests or restructure the directories to have an increasing level of testing difficulty.. An example would be:

./py_unittest_walkthrough
  ./getting_started
    ./bin
    ./src/funprog
    ./test
  ./argparse_unittests
    ./bin
    ./src/argparse_fun
    ./test
  ./class_testing
    ./bin
    ./src/class_testing
    ./test
...

Where each directory contains a testing suite. I prefer using directories rather than branches but this would need to be reflected in the README. Thoughts @rjbeers @xanderyzwich

@xanderyzwich
Copy link
Member

I'd prefer the directory approach as I believe it would be more intuitive to 'users'

@drkennetz drkennetz added the hacktoberfest issues good for hacktoberfest label Oct 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request hacktoberfest issues good for hacktoberfest
Projects
None yet
Development

No branches or pull requests

3 participants