path: root/wiki/src/contribute/working_together/roles/test_suite.mdwn
diff options
Diffstat (limited to 'wiki/src/contribute/working_together/roles/test_suite.mdwn')
1 files changed, 8 insertions, 1 deletions
diff --git a/wiki/src/contribute/working_together/roles/test_suite.mdwn b/wiki/src/contribute/working_together/roles/test_suite.mdwn
index f10513e..af78480 100644
--- a/wiki/src/contribute/working_together/roles/test_suite.mdwn
+++ b/wiki/src/contribute/working_together/roles/test_suite.mdwn
@@ -14,8 +14,15 @@ test suite by:
- Writing tests for regressions, unexpected or unbudgeted features, etc.
+ - Refactoring the test suite code as needed, whenever we're trying
+ to solve another practical problem, and the lack of refactoring
+ gets in the way. In other words: refactoring will be dealt with by
+ test suite maintainers as a integral part of modifying code, and
+ not as a separate task.
Writing tests for new features should be estimated and budgeted each
-time we write grant applications for such features.
+time we write grant applications for such features. Same for the
+refactoring that such work may require.
Writing tests to replace our old manual tests should also be budgeted