Add more robust tests about blui-cli HOT 4 OPEN

Some more test ideas:
Unit tests for our custom functions, like the custom printing function, checking for the flags, checking for the file extension when ts is set

from blui-cli.

I would like to clarify what some of the "Unit tests for the commands and extensions" would be in our next bug scrub so we can either add more detail to this issue or close it.

from blui-cli.

Let's rewrite this issue to be more specific about what kinds of tests we want to have. Would be a good idea to get a code coverage report before diving into further testing.

from blui-cli.

@emclaug2 I asked for yer

[11:29 AM] Boyle, Joseph P
(...)

Unit tests checking inputs generate the correct outputs for all of our utility functions, verifying that the correct files/contents are present in the generated file (e.g., does package.json have the correct dependencies in it, does the App.tsx file have the right contents, are typescript packages installed for javascript projects, is the eslint package only installed for packages that used that flag, etc.)

[11:33 AM] Boyle, Joseph P
That can be a pretty low priority issue though...the CLI may be a target for consolidation efforts / culling if we don't expect to build out additional functionality (we can just use our templates with the underlying CLIs and it's one less thing to maintain)

from blui-cli.