Page History

This page specifies the rules and guidelines for developers and QA when dealing with CloudStack's BVT and automated regression tests.

Why BVT and

...

Regression Tests

CloudStack deals with a wide range of hardware resources physical and virtual resources.  It is impossible for anyone any one developer/QA to test if their feature/functionality works across all of the supported resources.  CloudStackCloudStack's BVT and automated regression tests provide a method for developers to submit their changes to be tested across the supported infrastructure.  It also allows support for  Physical/Virtual resource providers can also donate their resources and tests to the BVT and regression test systems.  

Principles

• BVT and Regression Tests must be fully automated.  This means it is automated in all phases: deployment, setup, execution, reporting, and bug filing.
• Any code that breaks BVT and Regression Tests on master and all release branches must be reverted.
• Any code that breaks BVT and Regression Tests on feature branches will be marked as P0 bug for that feature.
• All tests are maintained by developers and QA.  If a feature changes CloudStack behavior to cause a breakage in the tests, it is the feature developer/s responsibility to fix the tests 

How to donate hardware/software for integration testing

Rules and Guidelines for Developers and QA

Principles behind