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

Test coverage #20

Open
kasparsklavins opened this issue Mar 13, 2017 · 4 comments
Open

Test coverage #20

kasparsklavins opened this issue Mar 13, 2017 · 4 comments
Assignees
Labels

Comments

@kasparsklavins
Copy link
Owner

Just a reminder to eventually add test coverage.

@ghost
Copy link

ghost commented Mar 13, 2017

You could have a look at my test-suite and may give you some ideas TitanSnow:bigint

@kasparsklavins
Copy link
Owner Author

Good idea testing against python.

But I dont want to add another language in the build script.

@MahmoudRizk
Copy link
Contributor

I think , you can generate the test cases and their answers saved in a file. @titansnow

@ghost
Copy link

ghost commented Mar 14, 2017

That sounds not so interesting as random test cases, right? @MahmoudRizk There are always situations that people cannot predict and think out. Oh I forget to say that to start testing just make test. (Forgive me, I don't know cmake enough so I use Makefile instead) I add it to travisCI so each time I push, it will take the server about 5 minutes to test it 😃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants