dorotaphanSiili
commented
1 year ago Idea: maybe the performance tests should be on separate branch like performance -apigear -cpp14 -qt -unreal (at some point) -and more -test_runner <-with some scripts that will run cross technology
it would have to be run maybe once a day? generate code for all technologies from their main branches and build all we should define what "pass" means maybe store all pass 100 results and check that current (run like 100times each) is not worse than average + 5%?
This is initial commit with initial test for only one object sending many messages. The difficulty of testing many nodes is, that it requires classes with different object id which needs: either many different interface classes or editing the generated code. ALSO Tests are not build with CI, but at some point they should be added. The downside is that solution need to be regenerated (although otherwise they might got old) To use it under the visual studio performance profiler I needed to change generated cmakes to fetch poco lib (which is not delivered)