linebender / android_trace Goto Github PK

The sync layer has some nasty code to manage the stack. E.g. (up-to-date at the time of writing):

We should find a way to test this code. This would involve:

1. Enabling mocking AndroidTrace for testing, somehow (either with a trait, or by specifying the function calls directly)
2. Creating a layer which uses this mocked AndroidTrace
3. Running tests with different timings of enabled/disabled and span creation/exiting
4. Saving the resulting trees, and seeing if they make sense (probably with a kind of snapshot testing), + that each open of a span is met with a matching close

This is not a high priority