Devise a way of testing the kernel. about ppytty HOT 4 CLOSED

CRAZY IDEA:

• What if scheduler.run() or scheduler.schedule(...) was iterable?
• That would support two possibly useful things:
  • Testing: by iterating by hand and checking kernel state between iterations.
  • REPL based interaction: where some commands would move the scheduler forward.

Hmmm... Interesting.

POST NOTE: Not literally iterable (as in a Python iterable), but the just merged #75 supports manual "move forward" of the kernel inner loop.

from ppytty.

Progress note:

• With the merge of #32 and #38 we probably no longer need a special test terminal.

from ppytty.

More ideas... Maybe:

• run / schedule could be told to run a single iteration.
• The built-in, hard-coded terminal could no longer exist: tasks would "allocate" / "deallocate" it at runtime.

from ppytty.

CLOSING NOTES:

• Kernel is definitely testable.
• It is mostly tested, actually.
• Most tests are integration-like: a custom set of tasks is run, and assertions are completed once the test-driving-task(s) are completed.
• There is, however, one test that demonstrates the capability of testing the inner kernel loop in a step by step way.
• A few, somewhat messy helper classes deal with I/O and time during tests. These could certainly be improved and, maybe, simplified.
• The idea of multiple terminal lives on: see #76.

from ppytty.