You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Applying the template to existing code with tests creates dummy test files #578
The template creates the dummy test files tests/test_my_module.py, tests/test_values.py, and tests/test_projects.py when I apply it to code which already has tests in a tests/ folder. This is not really necessary I believe. Of course these files can be deleted, but users might accidentally commit them or forget to delete them.
I think #594 is different. This issue is for when you have the local tests folder, and you probably want to say yes to having local tests. Saying no after #594 will prevent the issue, but won't solve for the general case.
On Bestie, all users have a test/runtests.jl file. That's the entry point to our equivalent to pytest. So it's predictable.
Is it common to have some main test file, like tests/test_<package_name>.py, for instance?
PS. The other two files test_values.py and test_projects.py, don't seem to be present anymore.
Activity
fdiblen commentedon Aug 28, 2024
Ref: #594
abelsiqueira commentedon Aug 29, 2024
I think #594 is different. This issue is for when you have the local
testsfolder, and you probably want to sayyesto having local tests. Sayingnoafter #594 will prevent the issue, but won't solve for the general case.On Bestie, all users have a
test/runtests.jlfile. That's the entry point to our equivalent topytest. So it's predictable.Is it common to have some main test file, like
tests/test_<package_name>.py, for instance?PS. The other two files
test_values.pyandtest_projects.py, don't seem to be present anymore.