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 framework for half-resolved issues #16

Closed
AlexDaniel opened this issue Jun 25, 2018 · 0 comments
Closed

Test framework for half-resolved issues #16

AlexDaniel opened this issue Jun 25, 2018 · 0 comments
Assignees
Labels
testneeded Issue is generally resolved but tests were not written yet

Comments

@AlexDaniel
Copy link
Member

AlexDaniel commented Jun 25, 2018

There are several open tickets with testneeded label and it would be nice to close them with tests. In whateverable I mainly do system testing, so every test is a command that is sent to the bot on an actual IRC server. While some would consider this approach improper (at least when used alone without unit tests), I feel more comfortable knowing that the functionality is tested thoroughly in an exhaustive manner. This helped me reveal memory issues, left file handles, segfaults and other issues in rakudo from whateverable test suite. Maybe something like that should be implemented for sake also (i.e. a testing framework that runs actual Sakefiles, looks at results and cleans up).

@AlexDaniel AlexDaniel added the testneeded Issue is generally resolved but tests were not written yet label Jun 25, 2018
@AlexDaniel AlexDaniel self-assigned this Jul 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
testneeded Issue is generally resolved but tests were not written yet
Projects
None yet
Development

No branches or pull requests

1 participant