summaryrefslogtreecommitdiff
path: root/topics/testing/automated-testing.gmi
diff options
context:
space:
mode:
authorArun Isaac2022-02-10 14:16:08 +0530
committerArun Isaac2022-02-10 14:16:08 +0530
commitf1bd9dbeb8aa51c2f555150168f1933c502d5951 (patch)
tree9f1d9d409724f81652185e73cb6a08a878ac7bab /topics/testing/automated-testing.gmi
parent44590da2ffea59e4d4971287233fa1b4f37f4cc4 (diff)
downloadgn-gemtext-f1bd9dbeb8aa51c2f555150168f1933c502d5951.tar.gz
Comment on testing interface for automated tests.
Diffstat (limited to 'topics/testing/automated-testing.gmi')
-rw-r--r--topics/testing/automated-testing.gmi4
1 files changed, 3 insertions, 1 deletions
diff --git a/topics/testing/automated-testing.gmi b/topics/testing/automated-testing.gmi
index 3f85301..378a641 100644
--- a/topics/testing/automated-testing.gmi
+++ b/topics/testing/automated-testing.gmi
@@ -86,4 +86,6 @@ There might need to be checks for responsiveness built in.
Checks that previously working features are not broken. These can be added as we go along
-## [[OTHER SYSTEMS GO HERE]]
+## Testing interface
+
+Tests in different categories should be grouped into different command-line endpoints. For example, unit tests could be run by "python3 setup.py check", integration tests could be run by "python3 setup.py integration-check", performance tests could be run by "python3 setup.py performance-check", and so on. This way, the CI will have to be configured only once, and then committers will be able to add new tests without requesting for a CI reconfiguration each time. We won't have to wait on others to respond. Less coordination will be required leading to smoother work for everyone.