gce-api/HACKING.rst
Alexandre Levine 754725a4aa GCE-API support service for OpenStack
Change-Id: I80f6b024cb40ba31ebaacf35d7364f66115da9c6
Implements: blueprint gce-api
2014-02-04 19:16:29 +04:00

1.3 KiB

Gceapi Style Commandments

Gceapi Specific Commandments

General

  • Do not use locals(). Example:

    LOG.debug(_("volume %(vol_name)s: creating size %(vol_size)sG") %
              locals()) # BAD
    
    LOG.debug(_("volume %(vol_name)s: creating size %(vol_size)sG") %
              {'vol_name': vol_name,
               'vol_size': vol_size}) # OKAY
  • Use 'raise' instead of 'raise e' to preserve original traceback or exception being reraised:

    except Exception as e:
        ...
        raise e  # BAD
    
    except Exception:
        ...
        raise  # OKAY

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 Gceapi, please read gceapi/testing/README.rst.