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

Way to add new tests of our own to a problem #8

Closed
GaurangTandon opened this issue May 18, 2019 · 2 comments
Closed

Way to add new tests of our own to a problem #8

GaurangTandon opened this issue May 18, 2019 · 2 comments
Labels
good first issue Good for newcomers

Comments

@GaurangTandon
Copy link
Contributor

Hi, thanks for the wonderful tool! I have a feature request.

Before submitting the problem, I usually do a few sample tests of my own too. Currently, I maintain an input file, so once I've thought and written a test, I won't have to retype it again.

With your setup, I feel I could be more productive in doing so. So, basically, I'll run a command like cf add-test. Then you'll prompt me for the input and the output, and then put them into files inK.txt and ansK.txt (K = integer) inside my working directory. So, that the next time I run cf test, these files will also be checked for correctness.

Thoughts? I don't know much golang but if you need help I'll be more than happy to help out.

@GaurangTandon GaurangTandon changed the title [Feature request] Way to add new tests of our own to a problem Way to add new tests of our own to a problem May 18, 2019
@xalanq
Copy link
Owner

xalanq commented May 18, 2019

Actually you can create the extra sample files inK.txt and ansK.txt if both files are not exist.
But I'll consider to add it.

@xalanq
Copy link
Owner

xalanq commented May 19, 2019

I think the way above is simple enough. I'll add this way in README.

@xalanq xalanq closed this as completed May 19, 2019
@xalanq xalanq added the good first issue Good for newcomers label Jul 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants