[ckan-changes] [ckan/ckan] cc7e91: [#1697] Don't break PEP8 tests if test files have ...

Thu May 1 22:49:40 UTC 2014

  Branch: refs/heads/1697-dont-validate-e501-on-tests
  Home:   https://github.com/ckan/ckan
  Commit: cc7e91743d179964dcf271875bc10db64b6fc0c9
      https://github.com/ckan/ckan/commit/cc7e91743d179964dcf271875bc10db64b6fc0c9
  Author: Vitor Baptista <vitor at vitorbaptista.com>
  Date:   2014-05-01 (Thu, 01 May 2014)

  Changed paths:
    M ckan/tests/test_coding_standards.py

  Log Message:
  -----------
  [#1697] Don't break PEP8 tests if test files have lines >79 chars

According to naming test methods [1] in our testing coding standards, we should
make the test names clear "...even if it means your method name gets really
long, since we don’t write code that calls our test methods there’s no
advantage to having short test method names".  Given this, we shouldn't
validate E501 on our test suite.

[1] https://ckan.readthedocs.org/en/latest/contributing/testing.html#naming-test-methods