Hi Folks, so in the plc4go branch I did the changes and all of the adjustments in the tests this change needed. In the end it seems I needed to go down the "test-jar" path as "provided" resources don't seem to be included in the default classpath and I therefore couldn't load them. But with the test-jar it works nicely.
Chris Am 14.10.20, 12:51 schrieb "Christofer Dutz" <[email protected]>: And I will put them in the "src/main/resources" directory. The mspec is used for the code generation and isn't bundled with the driver. If I put it in "src/test/resources", this would make packaging and using it more difficult. Chris Am 14.10.20, 12:50 schrieb "Christofer Dutz" <[email protected]>: Ok ... so I'll do this in my plc4go branch. If you happen to need that for python ... just ping me. Chris Am 14.10.20, 12:48 schrieb "Otto Fowler" <[email protected]>: +1 On October 14, 2020 at 05:38:26, Christofer Dutz ([email protected]) wrote: Hi all, currently the Java drivers are the only ones having support for the XML testsuites I built. Now I would like to setup the same testsuite infrastructure for my PLC4Go drivers. For that I would need the same XML test-definitions. So I thought, and I think we discussed this at least on slack before, it would be cool to move these test-definitions into the protocol modules. This way we can define the mspecs and provide tests for the mspecs which are theoretically runnable on all platforms in the same module. So if we extend an mspec and add some additional test declarations, these should automatically run in all languages we support. What do you think? Chris
