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

Testing #11

Open
asofold opened this issue Sep 21, 2013 · 0 comments
Open

Testing #11

asofold opened this issue Sep 21, 2013 · 0 comments
Labels

Comments

@asofold
Copy link
Member

asofold commented Sep 21, 2013

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.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant