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

Integration Tests #15

Closed
2 of 5 tasks
arm4b opened this issue Aug 19, 2015 · 2 comments
Closed
2 of 5 tasks

Integration Tests #15

arm4b opened this issue Aug 19, 2015 · 2 comments

Comments

@arm4b
Copy link
Member

arm4b commented Aug 19, 2015

Before publishing on Ansible Galaxy, add some Integration/Smoke tests, increase infrastructure coverage.

Infrastructure Testing Frameworks

  • Evaluate ServerSpec / InSpec - ruby-based. Famous, big community, nice looking and best in his class. But the team prefers Python (st2 main lang).
  • Evaluate BATS - Bash Automated Testing System, which is a bit easier.
  • Evaluate TestInfra - Python-based infra testing framework. Still pretty young, very small community. Intro.

Automation

  • Molecule project - automation for testing Ansible roles
  • TestKitchen - automation to spin up Vagrant or Docker or even AWS instance and test Ansible roles with Serverspec/BATS against just spinned up machines.

More info: http://stackoverflow.com/a/37006819/4533625
Continue work started in #7

@arm4b arm4b added this to the v0.3.0 milestone Aug 19, 2015
@arm4b arm4b changed the title More Rspec Tests More Integration Tests Aug 26, 2015
@arm4b arm4b mentioned this issue Apr 4, 2016
4 tasks
@arm4b arm4b changed the title More Integration Tests Integration Tests May 6, 2016
This was referenced May 6, 2016
@jvrplmlmn
Copy link
Contributor

I'd personally go for InSpec. Most of the code from StackStorm/chef-stackstorm#29 can be re-used here.

@arm4b
Copy link
Member Author

arm4b commented Jul 28, 2020

https://github.com/StackStorm/ansible-st2/tree/master/test/integration somewhat serves the purpose. Nightly CI Travis jobs that test both stable and development st2 versions even spot several regressions in st2 core before other stackstorm e2e tests could catch it.

@arm4b arm4b closed this as completed Jul 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants