Build: Separate acceptance testing infrastructure into stand-alone environment

Currently we have all of our testing infrastructure merged into our various environments. This introduces extra complexity into our build scripts and also makes it difficult to support changes just within the testing infrastructure e.g. updating version of Gems required by tests only.

To make life easier for running and creating acceptance tests for the developers.redhat.com project, we should migrate the current acceptance testing infrastructure into its own environment

Important

This user story is about creating a new approach for running the acceptance tests. It does not involve the removal of the current approach for existing build scripts. The old approach to executing the acceptance tests will remain but should be considered deprecated and will be cleaned-up at a later date.

Definition of Done

• Acceptance tests have their own environment definition that is separate from our current environments
• Acceptance tests have their own run scripts
• Acceptance tests can have their own dependencies and can update these independently of the main developers.redhat.com project
• Jenkins can run acceptance tests for pull requests and also for other scenarios e.g. nightly builds using the separated environment
• Updates to Github statuses etc. continue to work as expected