Closed ulfox closed 3 years ago
The issue was due to a missconfigured test. The value expected value from 2 different scenarios was the same.
That lead assert to pass both scenarions while it should have faild on the second
Now tests have been updated and the wrong condition that was returning a wrong value fixed
The issue was due to a missconfigured test. The value expected value from 2 different scenarios was the same.
That lead assert to pass both scenarions while it should have faild on the second
Now tests have been updated and the wrong condition that was returning a wrong value fixed