Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] unit test for consistency of property editors [sf#44] #6

Open
patrickwestphal opened this issue Feb 4, 2015 · 0 comments

Comments

@patrickwestphal
Copy link
Member

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.

@patrickwestphal patrickwestphal changed the title unit test for consistency of property editors [Feature] unit test for consistency of property editors [sf#44] Feb 4, 2015
@patrickwestphal patrickwestphal added this to the 1.5 milestone Mar 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant