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.

Sign up for GitHub

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

Jump to bottom

Good way to test changes #92

Open
rizend opened this issue Dec 10, 2018 · 1 comment
Open

Good way to test changes #92

rizend opened this issue Dec 10, 2018 · 1 comment

Comments

@rizend
Copy link
Contributor

rizend commented Dec 10, 2018

I know of no good way of testing my changes right now. People have suggested deploying to a test server, but AFAICT the os and version needed are not documented (see #91 ). Opening PRs with a guess at what will work and then waiting for someone with access to the server(s) affected to check the PR is rather slow and, if the changes don't work, could cause issues with the production servers. I think this could be alleviated by having a testing server that is relatively easy to get access to.
@SuperQ
Copy link
Collaborator

SuperQ commented Dec 10, 2018

We could do ansible unit testing with Molecule.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@SuperQ @rizend