What is the problem?
You found a solution for a bug, an improvement or you just wrote the next-level importer for some asset-format everyone wants to use. So how will be sure that everything is working as expected?
The solution
Just use our CI chain which is provided on GitHub. There you will get feedback in various forms:
- The code will be build for Windows, Linux, and iOS
- All unittests will be performed on each platform
- For each platform code analysis will be performed. Here we are using the Sanitizers coming with clang. You can test the code for Meory leaks (attention: the leak must be visible in the unittests), misaligned memory for embedded platforms (not all architectures are fine when you are trying to perform a dynamic cast on a not aligned piece of memory), any kind of multi-tread issues and undefined behavior.
- The code will get checked by a static code analysis tool automatically.
- The Google Fuzzer project is testing your stuff every night
So if your code has any kind of issues the CI will help you make it fine. Just write a unittest for your work. This helps a lot to check your work.
And thanks for yll your support!
