You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by jenslehmann on 2011-08-18 08:31 UTC
There should be a unit test for the various implementations of the PropertyEditor interface in DL-Learner, which checks whether setAsText and getAsText are consistent, i.e. first calling setAsTest(String) and then getAsText should result in the same string for all editors and all valid strings.
The text was updated successfully, but these errors were encountered:
patrickwestphal
changed the title
unit test for consistency of property editors
[Feature] unit test for consistency of property editors [sf#44]
Feb 4, 2015
Reported by jenslehmann on 2011-08-18 08:31 UTC
There should be a unit test for the various implementations of the PropertyEditor interface in DL-Learner, which checks whether setAsText and getAsText are consistent, i.e. first calling setAsTest(String) and then getAsText should result in the same string for all editors and all valid strings.
The text was updated successfully, but these errors were encountered: