Conversation
|
Hey there! Thanks for helping Mudlet improve. 🌟 Test versionsYou can directly test the changes here:
No need to install anything - just unzip and run. |
|
It is possible to leave the pending stubs but not have them clutter the output, either through setting the suppressPendings option in the script in run-tests.xml or by removing the second argument to the pending() calls. When using the TAP output it shows as Ok and skipped, so shouldn't halt CI to leave them reported, but could get unwieldy if we stub a lot of tests. That being said, the end goal is to get as close to 100% coverage as possible, and having it tell how many pending tests are still to write is potential motivation for writing them and also shows progress as the number on the right goes down and the one on the left goes up. |
keneanung
left a comment
There was a problem hiding this comment.
I'm fine with the pending output staying as it is.
* Fixing typo in error message for table.is_empty * Adding tests and increasing coverage for TableUtils spec.
Brief overview of PR changes/additions
Motivation for adding to Mudlet
TEST ALL THE THINGS!
Other info (issues closed, discussion etc)