You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have had issues with bats in the past (leaving long-running processes when a test fails), and while getting native TAP output is nice, debugging failing tests was challenging -- especially when the script has multiple tests.
Another issue users who build/instal FRE-NCtools may not know that test will only run if bats is installed, and in the user's PATH -- as configure.ac doesn't fail if bats is not found. We should rewrite the tests not to use bats.
The text was updated successfully, but these errors were encountered:
We have had issues with bats in the past (leaving long-running processes when a test fails), and while getting native TAP output is nice, debugging failing tests was challenging -- especially when the script has multiple tests.
Another issue users who build/instal FRE-NCtools may not know that test will only run if bats is installed, and in the user's PATH -- as configure.ac doesn't fail if bats is not found. We should rewrite the tests not to use bats.
The text was updated successfully, but these errors were encountered: