Skip to content
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

Automated integration testing for parent commands #46

Closed
wintondeshong opened this issue Jan 10, 2020 · 2 comments
Closed

Automated integration testing for parent commands #46

wintondeshong opened this issue Jan 10, 2020 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@wintondeshong
Copy link
Contributor

There is an increasing likelihood for regressions as the code base grows from an actual integration perspective. Investigate options for adding automated integration tests for our parent commands.

Example:

@wintondeshong wintondeshong added the enhancement New feature or request label Jan 10, 2020
@brandongregoryscott
Copy link
Contributor

I'll take a stab at this. I have a working proof-of-concept on my fork. My plan is to clean it up and add a simple test or two for each parent-level command - something like "it displays the help menu." This should at least catch runtime errors in the command itself or imported modules that are called. 😅

We can look into expanding upon this and setting up integration tests for some of the higher risk commands (dotnet, webpack, etc.)

@brandongregoryscott
Copy link
Contributor

Closed by #70

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants