tasks: ideas about testing

Signed-off-by: Riku Viitanen <riku.viitanen@protonmail.com>

site/tasks/index.md

@@ -2423,3 +2423,37 @@ interesting video
 =================
 
 <https://www.youtube.com/watch?v=5qauRh7eTNY>
+
+Automate testing
+================
+
+Even though there's lots of error handling, it's better to be paranoid than
+brick users' machines.
+
+Unit tests
+----------
+
+- Build time or separate?
+- me_cleaner -c: checks that ime was inserted and has valid signatures
+
+CI
+--
+
+Preferably self-hosted. Run tests for every commit. There could be tests of
+different size, and even a periodic nightly release could be done.
+
+Integrating this with an automated test stand would also be doable. At the
+very least, it would assure that the ROM images boot successfully.
+
+Board status
+============
+
+As the number of ports grows, it becomes harder to keep track of what works.
+Let's build a machine-readable repo documenting every release (or commit)
+on every board. What features/payloads work, maybe include errata text field.
+A HTML report could also be generated and published online.
+
+On top of this, an easy to use installer could be developed. It would know
+to not install an unbootable (broken) ROM, and would inform users about any
+known problems and have meaningful options.
+