Juan Lang wrote:
Hi Paul,
Are the tests in devinst.c supposed so be run in order? IOW are they supposed to bee cleaned up after each subtest or do they rely on each other?
I'm sure I didn't put that much thought into making the tests order dependent. I wrote them, ran them, made them into tests, and they worked at least once for me. I might not have tested running them subsequent times on the same machine.
I don't think it's a general problem with the devinst.c tests. There are two problems with them:
- Some of the last error checks fail on some versions of Windows. I
only have Windows XP, so I couldn't have anticipated these. James is doing a nice job of cleaning them up (thanks James.) 2. The call to SetupDiRegisterDeviceInfo leaves keys around that are hard to delete, and cause subsequent runs of the test to fail.
In my opinion it's probably okay to remove the SetupDiRegisterDeviceInfo tests. I don't know any apps that call this API directly. --Juan
Now you tell me :-).
I've something in place already to get rid of the stray registry keys. Just needs some more thought and tweaking.