Backfill tests for user-prompt module #88
Labels
enhancement
New feature or request
good first issue
Good for newcomers
hacktoberfest
Support hacktoberfest (not required to get credit)
Backfill tests for
user-prompt
moduleAs a general rule of thumb, I like to test exit paths (error or otherwise) to ensure the module is killing the process when expected. If we are returning from an erroneous
exec
orspawnSync
call , ensure we are forwarding the exit code properly. (Seedotnet-build.test.js
for an example of this)Add coverage where you see the most value - Jest will usually mark
description()
functions as having missed coverage, but seeing as we only use these for printing out text to the UI help menu, there's little value in testing that.While you're in there, consider renaming the file and any commands that import it to just
prompt
. Not sure why I named ituser-prompt
. Who else would we be prompting?The text was updated successfully, but these errors were encountered: