We can write test scripts, we can have a whole custom built test environment to switch in the OTS and we can exhaustingly test it.
The only thing we can not have is unit tests for unknown software code. But it also only true if we consider unit as it was defined at the first place by the source code developer/architect. We can define our understanding about the units and their interaction and test it, no problem.
There are OTSs for algorithms, frameworks, plugins, codexs, etc. , OTS is not necessarily visible and recognizeble by the end user.
Actually In my understanding unit tests is up to the discretion of the manufacturer and not necessarily written for a device itself too.
The only thing we can not have is unit tests for unknown software code. But it also only true if we consider unit as it was defined at the first place by the source code developer/architect. We can define our understanding about the units and their interaction and test it, no problem.
There are OTSs for algorithms, frameworks, plugins, codexs, etc. , OTS is not necessarily visible and recognizeble by the end user.
Actually In my understanding unit tests is up to the discretion of the manufacturer and not necessarily written for a device itself too.
Last edited: