On Tue Aug 23 11:32:46 2022 +0000, R��mi Bernon wrote:
Well it could also test generated files for compatibility. It's a bit more tricky because it's probably not worth checking that it's 100% identical but it could probably be done with a bit of post processing. In any case I think that testing parser successes and failures is already enough value to justify it.
A nice way to test generated files is to use it somehow. For header files, it's easy to achieve by writing a C file that #includes it, and maybe uses it in some interesting ways. For typelibs, it requires loading and analyzing or using them. We already have that in oleaut32 tests. The only thing we don't have is easy validating that data against midl, but, at least for typelibs, it could be done by extending existing tests.
For testing parser success it's as easy as adding the interesting bits to some IDL file in tests, it's not a new ability that we'd gain from PE midl.exe.
That leaves only parser failures and I don't find it a good enough justification, especially when there are other ways to achieve that.