Unexpected validation results if expected value is 0
icnocop opened this issue · comments
If the expected value in a validation table is 0, and the actual value cannot be parsed as a number, the test always succeeds.
For example, add and run the following test in "SpecBind.CodedUI.IntegrationTests\Features\DivListValidationTests.feature":
Scenario: Validate with 0
Then I see results grid list starts with
| Field | Rule | Value |
| Department Name | Equals | Economics |
| Budget | Equals | 0 |
Even though the Budget for the Economics department is actually "$100,000.00", this test succeeds.
Similar unexpected behavior exists when comparing with other types like DateTime and boolean.