openstack
/
nova-powervm
Code Issues Proposed changes
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
stable/pike
stable/queens
stable/stein
stable/train
master
rocky-eol
ocata-eol
train-em
stein-em
rocky-em
9.0.0
9.0.0.0rc1
8.0.0
8.0.0.0rc2
8.0.0.0rc1
7.0.0
6.0.2
7.0.0.0rc2
7.0.0.0rc1
7.0.0.0b3
7.0.0.0b2
7.0.0.0b1
6.0.1
6.0.0
6.0.0.0rc2
6.0.0.0rc1
6.0.0.0b3
5.0.3
6.0.0.0b2
5.0.2
newton-eol
6.0.0.0b1
5.0.1
liberty-eol
5.0.0
5.0.0.0rc1
5.0.0.0b4
5.0.0.0b3
mitaka-eol
5.0.0.0b2
4.0.1
5.0.0.0b1
4.0.0
3.0.3
4.0.0.0rc2
4.0.0.0rc1
4.0.0.0b3
liberty_eol
4.0.0.0b2
3.0.2
3.0.1
3.0.0
3.0.0.0rc2
3.0.0.0rc1
3.0.0.0b3
3.0.0.0b2
2.0.3
3.0.0.0b1
2.0.2
2.0.1
2.0.0
2.0.0.0rc1
2.0.0.0b3
1.0.0
1.0.0rc1
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'f68cd4fa2f'
${ noResults }
nova-powervm/HACKING.rst

807 B
Raw Blame History

Nova-PowerVM Style Commandments

Nova-PowerVM Specific Commandments

  • Follow the Nova HACKING.rst

Creating Unit Tests

For every new feature, unit tests should be created that both test and (implicitly) document the usage of said feature. If submitting a patch for a bug that had no unit test, a new passing unit test should be added. If a submitted bug fix does have a unit test, be sure to add a new one that fails without the patch and passes with the patch.

For more information on creating unit tests and utilizing the testing infrastructure in OpenStack Nova, please read nova/tests/README.rst.