Skip to content

Applying the template to existing code with tests creates dummy test files #578

Open

Description

@maltelueken

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.

Activity

  1. added
    generated-packageRelated to the generated package, i.e. after running cookiecutter
    on Aug 27, 2024
  2. fdiblen commented on Aug 28, 2024

    @fdiblen
    Member

    Ref: #594

  3. abelsiqueira commented on Aug 29, 2024

    @abelsiqueira
    Member

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    generated-packageRelated to the generated package, i.e. after running cookiecutter

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions