Jira (PUP-7432) Improve Test Workflow

[Eric Thompson (JIRA)]

Title: Message Title

Eric Thompson commented on PUP-7432   Re: Improve Test Workflow test process for puppetdb as one example (i don't think we want to mimic this, exactly): ✓ erict@erict-mbp ~/projects/puppetdb2 ((3859072...))$ be rake -T rake beaker:acceptance[test_files] # Run beaker based acceptance tests rake beaker:first_run[test_files] # Run beaker based acceptance tests, leaving VMs in place for later runs rake beaker:list_vms # List your VMs in ec2 rake beaker:performance[test_files] # Run beaker based performance tests rake beaker:rerun[test_files] # Re-run beaker based acceptance tests, using previously provisioned VMs rake package:bootstrap # Bootstrap packaging automation, e.g rake package:implode # Remove all cloned packaging automation for us (puppet agent), the main switch seems to be mode; this is historically namespaced into different task names. one idea would be to use more generic tasks and namespaces and specify mode as an argument to the task other things we need to specify are a puppet SHA or a PA suite_commit, host pattern, test_files these are historically provided by environment variables. SHA/commit and test targets are in environment variables in CI, so they should probably remain there. list of files to test has historically been in an env var as well. let's discuss the correct interface, moving forward. i'd like to use this as a test-bed for a task supplied by beaker/bhg itself. Add Comment   This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.