-
Notifications
You must be signed in to change notification settings - Fork 300
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
Set up test suite #45
Comments
I've now implemented a basic test suite. As said, the testsuite is very simple: just parse two folders consisting of text files: "/tests/false_positives" The test is successful if any string in any text file of "false_positives" is not detected by the txt list and any string in any text file of "false_negatives" is detected by the txt list. Can you have a look at the fork if that generally fits your expectations?
For code changes, see this commit. If yes, I would integrate GitHub Actions and make a pull request for this repository. |
Did you have a chance to have a look at the test suite? Thanks :) |
Any update on this? |
1 similar comment
Any update on this? |
Sorry, I haven’t had a chance to give this much time. Moving it up my priority list, though. |
Yes, I can contribute by adding a testsuite in one of the following environments
Do you have any preference or suggestions on these environments?
Personally I would make the testsuite very simple: just parse two folders consisting of text files, the folders could be named something like:
The test is successful if any string in any text file of "false_positive" is not detected by the txt list and any string in any text file of "false_negative" is detected by the txt list.
Then run that testsuite on GitHub Actions (before every merge).
That would be cool, what do you think?
Originally posted by @vielhuber in #44 (comment)
The text was updated successfully, but these errors were encountered: