Testsuite Framework

[dd86k]

Obviously, unit testing can only cover a portion of code.

For the shell and other modules that require external tests, it'll be worthwhile to create a D script.

Things to test:

• Shell commands.
• Fuzzing input for object server.

tester.d:

• Compiles and runs example programs found in tests/automated/.
• May need to finish some APIs first.
• Support for Fuzzing (especially object server).
  • Either zzuf or AFL.
• Could be nice to check version (--ver)

[dd86k]

It would be so much more worthwhile making a shared object build type first. This avoids the need to rely on a debug server (e.g., DAP, GDB/MI).

Which the test framework will use.

The test framework could load it first thing and provide either a shell or a list of options (by default) to test (tests can still be selected using switches).

Tests:

• compileall: Compile all configurations, architecture, and build types.
  • Note: CI only tests the most used build configurations.
  • matrix(string[]...), e.g., matrix(["1"], ["2"], ["3"]) -> [0]: ["1", "2", "3"]
• debugger-spawn: Spawn bogus process by debugger and expect a loaded status, etc.