Skip to content
This repository was archived by the owner on Aug 26, 2023. It is now read-only.
This repository was archived by the owner on Aug 26, 2023. It is now read-only.

Testing #11

Description

@asofold

Since it is not certain where we will put which class/component things will keep changing for a while, but we should decide in time to what degree we want to integrate (unit-) testing.

Of course we can add tests at any point of time, but suggest to attempt one of the following:

  • Write tests for any testable feature from the start, features that need testing in a running environment should lead to a documentation entry (where?) about how to test it and why.
  • Less strict: At least add tests/doc for things we can't overlook at once (like above), add actual tests/docs at least with every bug that is reported/fixed.

Activity

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions