| --- | --- |
| Bugzilla Link | 578240 |
| Status | UNCONFIRMED |
| Importance | P3 normal |
| Reported | Jan 17, 2022 05:14 EDT |
| Modified | Jan 17, 2022 05:14 EDT |
| Reporter | Benedek Horvath |
Description
At the moment, in the ViatraQueryTest builder the with method sets both the actual and the expected result, depending on the order in which it is called. The first call of the with sets the actual result and the second call set the expected result.
From the API user's perspective it would be better if there were different method for setting the actual and the expected results, e.g. withExpected, withActual, to avoid confusion.
| --- | --- | | Bugzilla Link | 578240 | | Status | UNCONFIRMED | | Importance | P3 normal | | Reported | Jan 17, 2022 05:14 EDT | | Modified | Jan 17, 2022 05:14 EDT | | Reporter | Benedek Horvath |
Description
At the moment, in the ViatraQueryTest builder the
withmethod sets both the actual and the expected result, depending on the order in which it is called. The first call of thewithsets the actual result and the second call set the expected result.From the API user's perspective it would be better if there were different method for setting the actual and the expected results, e.g. withExpected, withActual, to avoid confusion.