Additional testing opportunities

[LinqLover]

TDBCursor

• analogously to #testTraceSimple, add acceptance test for recorded states somewhere?
• test #isContextAlive:
• test stepToHome: with foreign contexts (see examples in stepToHome:)
• test stepThrough: from sender

Kernel tests

• These tests currently do not include the building of a trace (only side-effects are traced).

  We should discuss whether this reveals a bad design of the tracing simulator (the tracing simulator is not responsible for building the trace; the cursor/trace does that) or whether we should talk to the cursor directly in some of the kernel tests.

• Smart smoke assumptions for kernel tests: For instance, reevaluate each test twice and compare the second execution to the trace of the first one. Reevaluation Reevaluate trace #24 would give us further possibilities here.

• Compare trace with normal execution? This would not work for details of SimulationContext.

UI

• test spawn & process termination

General concerns

• Improve primitive tests in the simulated code (such as WriteBarrierTest)
• Run all tests without useProxiesAlways (CI config?)