I am running into some cases where OpenTAP “helpfully” removes instruments from the configuration that it can’t find because they are disconnected or powered off. Is there a way to change this behavior to error and stop testing instead of trying to test by removing the configured item and then giving errors because the test steps reference something that doesn’t exist? I honestly find it a bit absurd that it changes the bench configuration files at all. Those should be read-only to OpenTAP.
Will it do this to DUTs too? Our DUTs are never powered until after the setup phase of testing is complete (checking for shorts and opens, etc). It would be particularly bad if it removed the DUTs before the test even began.
I don’t recognize the exact problem you are mentioning here. OpenTAP will not remove resources, just because they are powered off or disconnected.
It makes me wonder if you have some plugin that does this.
Something I know happens is if you load a test plan that depends on resources that are not defined in your settings, but I believe this is different from what you describe.
Can you provide a path to reproducing what you are describing?
I’ve got the PathWave ks8000a license. Any time I add a device and then run a TapPlan, it deletes the device if the device isn’t immediately available at runtime.
For me, this happens every time. I originally set Instruments.xml to read-only so it wouldn’t, but once I deployed in my test runner that read-only flag caused OpenTAP to throw errors.
You’re making me think this might be a Keysight problem. I haven’t used OpenTAP without it because I’ve been developing tests and a test runner in parallel.