It's nice if testing doesn't produce unnecessary artifacts after running with success but keeps relevant info on fail for further inspection.

Pytest should have a nice way of creating fixtures that can post-process a test based on whether it failed or not https://docs.pytest.org/en/latest/example/simple.html#making-test-result-information-available-in-fixtures

If a test fails, then keep the

Tl;dr: building a simple DeepState testcase as shown below, gives the -Wmissing-noreturn warning. This might be an issue if DeepState is incorporated into a codebase that uses -Werror.

Example code

#include <deepstate/DeepState.hpp>

using namespace deepstate;

TEST(TestCaseName, TestName) {
        ASSERT(1);
}

Related build log

[1/2] Building CXX objec

Per #2, deque cannot be analyzed symbolically. Tentative plan is to implement a "dumb" version on top of a generic list: https://github.com/pschanely/CrossHair/blob/56ce14ee44c1103121c483f479d3d1a5a4bd3438/crosshair/simplestructs.py#L57

• Show positional parameter info whenever a call or return happens
• Show call stack somewhere

Real talk: we should get rid of the JS stateful morass and reimplement this all in Elm. (That's the part that's a "good student project".)