GothenburgBitFactory/taskwarrior
1
0
Fork 0
mirror of https://github.com/GothenburgBitFactory/taskwarrior.git synced 2025-08-20 04:13:07 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 6

Documentation

Browse source 
- Updated README.
This commit is contained in:
Paul Beckingham 2015-01-20 22:05:11 -05:00
parent a3490966c0
commit f4a6ec6f97
1 changed files with 8 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

8
test/README
View file

@ -32,6 +32,12 @@ There are three varieties of tests:
line, hooks and syncing. There is an example, 'template.t', that shows how line, hooks and syncing. There is an example, 'template.t', that shows how
to perform various high level tests. to perform various high level tests.
All tests are named with the pattern '*.t', and any other forms are not run by
the test harness. This allows us to rename tests (foo.t --> foo.x) to ensure
that they are not run. Sometimes tests are submitted for bugs that are not
scheduled to be fixed in the upcoming release, and we don't want the failing
tests to prevent us from seeing 100% pass rate for the bugs we *have* fixed.
Goals Goals
----- -----
@ -56,6 +62,8 @@ are:
* Eliminate obsolete tests, which are tests that have overlapping coverage. * Eliminate obsolete tests, which are tests that have overlapping coverage.
This means migrate bug-specific tests to feature tests. This means migrate bug-specific tests to feature tests.
* Categorize the tests, restructure the directories.
What Makes a Good Test What Makes a Good Test
---------------------- ----------------------