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.

Sign up for GitHub

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

Jump to bottom

Create a mechanism for the user to specify whether they want to write the test data back to the test file or not #98

Open
anujgandharv opened this issue Oct 15, 2013 · 1 comment
Open

Create a mechanism for the user to specify whether they want to write the test data back to the test file or not #98

anujgandharv opened this issue Oct 15, 2013 · 1 comment
Labels
enhancement

Comments

@anujgandharv
Copy link
Member

Some users have come back and said that they do not want to write the data back to the test file and they would like this feature to turn on or off as per their convenience.
Currently the only easy mechanism to do it is by extending the existing DataLoader implementations and override the writeData method to do nothing. Something like this : https://gist.github.com/anujgandharv/6988214

But there should be a cleaner mechanism to do it.
anujgandharv added a commit that referenced this issue Oct 16, 2013
@anujgandharv
Fixed issue #98.
b5835fa 
A user can now specify whether the test data should be written back to
the file or not using writeData attribute of DataLoader annotation or
using the system property "easeytest.writeData" that expects boolean
values.
anujgandharv added a commit that referenced this issue Oct 17, 2013
@anujgandharv
Fixed #95 , #96, #98
bd4518e
@anujgandharv
Copy link
Member Author

This is now available as part of the DataLoader annotation as well as a System Property "easytest.writeData".

@anujgandharv anujgandharv reopened this Oct 17, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@anujgandharv