Steps to reproduce:
1. Add a verification in a test to verify certain value is null
Actual: Despite of what value is set in the Verification it will not pass
Expected: To set 'null' or empty field so that the verification passes.
Posted on:28 Mar 2018 12:37
Thanks for sharing your ideas with us.
Please be informed that 'IsNull' and isNotNull' verifications were implemented in our R1 2018 (v.2018.1.130). If you have missed to upgrade to the latest release please give it a try to find out if this will fit your needs.
In case you have any concerns you could submit a support ticket to describe your difficulties and we will be happy to assist further!
Posted on:27 Mar 2018 20:23
Also it would be incredibly useful to be able to set an expected value returned in a response to be 0.0 (in this case is a metric for scoring and not actually null) and test studio to know the difference between Null and 0.0. Currently Null = 0.0 and vice versa when entered for an expectation.
Posted on:27 Mar 2018 20:09
Any ideas when or if this might be fixed in an update? The workaround is still functional, but horribly messy when trying to be efficient using Test Studio for APIs. Thanks.