1. 3

  2. 1

    I did something somewhat similar with my basic functionality test generator for a language bindings library that I had. The tests were generated using the same tooling used to generate the bindings, then the output for each function was controlled with a json file that allowed me to override the behavior. Using build.cs for this makes a lot of sense.

    I’m not quite sure if I’d do it the same way again in the future, but it was nice that I was getting effectively enforced 100% coverage (for my use case).

    This is old code that I’m not terribly proud of, but it works: https://github.com/rlabrecque/Steamworks.NET-TestGenerator https://github.com/rlabrecque/Steamworks.NET-Test