29 lines
1.1 KiB
ReStructuredText
29 lines
1.1 KiB
ReStructuredText
Networking-PowerVM Style Commandments
|
|
=====================================
|
|
|
|
- Step 1: Read the OpenStack Style Commandments
|
|
http://docs.openstack.org/developer/hacking/
|
|
- Step 2: Read on
|
|
|
|
Networking-PowerVM Specific Commandments
|
|
----------------------------------------
|
|
- Follow the Neutron HACKING.rst
|
|
|
|
- [P301] LOG.warn() is not allowed. Use LOG.warning()
|
|
- [P302] Deprecated library function os.popen()
|
|
|
|
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.
|
|
|
|
All unittest classes must ultimately inherit from testtools.TestCase.
|
|
|
|
All setUp and tearDown methods must upcall using the super() method.
|
|
tearDown methods should be avoided and addCleanup calls should be preferred.
|
|
Never manually create tempfiles. Always use the tempfile fixtures from
|
|
the fixture library to ensure that they are cleaned up.
|