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

Local Testing Workflow #10

Open
michaeltlombardi opened this issue Sep 14, 2018 · 0 comments
Open

Local Testing Workflow #10

michaeltlombardi opened this issue Sep 14, 2018 · 0 comments

Comments

@michaeltlombardi
Copy link

It'd be useful to be able to provide some sort of loosely prescriptive local testing workflow and aids.

Expected Behavior

AS A chocolatey package developer
I WANT to have tools to aid me in a prescriptive local testing workflow
SO THAT I can reduce cognitive overload for building and testing packages
AND SO THAT I can reduce the time to get production-ready packages
AND SO THAT I can test multiple platforms and conditions without leaving the editor

Current Behavior

I am mostly on my own (with the aid of docs and blogs) for managing my own testing workflow.

Possible Solution

Consider adding either a test-kitchen scaffold, vagrant boxes, or dockerfiles to a project workspace and a default script for building a package and testing it in the appropriate place.
Once how to test is figured out, enable management of the testing infrastructure and state from the command pallette.

Context

This would greatly reduce the amount of cognitive overhead required for getting into a local test-develop workflow.
Work done here could lead to easier testing specifications for CI as well.

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

No branches or pull requests

1 participant