From c8456f16afee8981a3d7a2d15b41b10d5841381b Mon Sep 17 00:00:00 2001
From: Munyoki Kilyungi
Date: Wed, 12 Oct 2022 16:20:06 +0300
Subject: Close issue on automated testing and create a separate topic for it

* issues/automated-testing.gmi: Close and point a link to the topic on
the same.
* topics/automated-testing.gmi: New topic.
---
 issues/automated-testing.gmi | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

(limited to 'issues/automated-testing.gmi')

diff --git a/issues/automated-testing.gmi b/issues/automated-testing.gmi
index a79245e..84e246c 100644
--- a/issues/automated-testing.gmi
+++ b/issues/automated-testing.gmi
@@ -3,7 +3,6 @@
 ## Tags
 
 * assigned: fredm, bonfacem, alex
-* status: in progress
 * priority: medium
 * type: enhancement
 * keywords: testing, CI, CD
@@ -138,3 +137,14 @@ For GN2 we should write scripts that test:
 ## 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.
+
+
+# Resolution
+
+This has been moved to it's own topic in:
+
+=> /topics/automated-testing.gmi Automated Testing
+
+Should there be anything actionable to be done, separate issues will be created.
+
+* closed
-- 
cgit v1.2.3