Post by lukaszpl on Dec 13, 2023 14:55:40 GMT
Hello,
Recently I've started using an Interop-Validator.
I'm going to recommend using of this tool inside my organization, but at this moment I see a kind of limitation(?), bug(?)...
In test report I can see that unexisting resources/properties that are 'Recommended' or 'IfImplemented' have a status: PASS.
It gives a false view on the status of service implementation.
Also, it requires additional tester's work to ensure which results are 'true' PASS.
From my perspective, if the object is not Mandatory and does not exist, then test should has a status: Not Applicable (NA).
Example:
![]()
![]()
![]()
![]()
And the second scenario...
it is related with a validation of Read/Write properties.
I see in the tool's helper an information, that 'writecheck' is not implemented.
I understand why you have decided to not implement that.
But I don't understand why InterOp still tries to validate both (Read/Write) properties...
'Read' is a default value - so if resource/property exists (we are able to read that), why we do a dobule check?
I think that tests for "ReadWrite" property should have a special status in the report, for example: Not Applicable (NA), or should be removed.
Example:
Cheers,
Lukasz
Recently I've started using an Interop-Validator.
I'm going to recommend using of this tool inside my organization, but at this moment I see a kind of limitation(?), bug(?)...
In test report I can see that unexisting resources/properties that are 'Recommended' or 'IfImplemented' have a status: PASS.
It gives a false view on the status of service implementation.
Also, it requires additional tester's work to ensure which results are 'true' PASS.
From my perspective, if the object is not Mandatory and does not exist, then test should has a status: Not Applicable (NA).
Example:
And the second scenario...
it is related with a validation of Read/Write properties.
I see in the tool's helper an information, that 'writecheck' is not implemented.
I understand why you have decided to not implement that.
But I don't understand why InterOp still tries to validate both (Read/Write) properties...
'Read' is a default value - so if resource/property exists (we are able to read that), why we do a dobule check?
I think that tests for "ReadWrite" property should have a special status in the report, for example: Not Applicable (NA), or should be removed.
Example:
Cheers,
Lukasz
