-
Notifications
You must be signed in to change notification settings - Fork 32
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
Create tests for WriteGDF.scala #55
Comments
We have 90% coverage on this one. We should cover this conditional which was not covered in #84: |
Not sure how to cover the results here. Either way, the function will return a Unit, (), so assertion will not work. Nor can I test for the function not creating a file. Would it be better if the function returned an Option or a Bool? |
…#64 & #66 (#87) * Add tests for remove Tuples, CreateGDF and RemoveHTML * Add RemoveHttpHeader test. * Add license header to tests. * Issues #56, #57, #58, #59, #61, #62 * resolves Issue #85 (JsonUtil) * Fix issue # 64 (ExtractDate coverage) * Resolve Issue #63 (Extract Domain coverage) * Fix error caused by repeated test names.
I think the solution for full coverage here is to ask the function to return a value on failure vs true. This can be an option or a Bool. (probably Bool). |
Cool. If you want to toss in a PR, let's see how it goes. |
It'll probably blow up some other test, but we'll see. :) |
Breaking shit, and blowing stuff up is how I learn 😃 |
🗡 💩 💥 💩 💩 |
* Minor fix to improve coverage. * Add ExtractBoilerpipe test. Improve ExtractBoilerpipe to avoid null pointer exception on null call. Add placeholders to ExtractEntities for further exploration. * Revise Write GDF to return a True on success and False on failure. Improve coverage on ExtractBoilerPipeText * Change test for empty path from if "" to if isEmpty().
Resolved with: 64a4851 |
WriteGDF.scala
has no test coverage. We need to create tests for it.The text was updated successfully, but these errors were encountered: