VirtualTam's bookmarks

21. SonarQube™ 2015-05-18

    tags: code, continuous-integration, development, inspection, quality

    [ permalink ]

    SonarQube is an open platform to manage code quality.

    https://github.com/SonarSource/sonarqube http://www.sonarsource.com/products/features/continuous-inspection/

22. How OpenStack Improves Code Quality with Project Gating and Zuul 2015-05-12

    tags: agile, build, continuous-integration, openstack, schedule, source-code-management/gerrit, taks, zuul

    [ permalink ]
23. Review of PHP Static Analysis Tools 2015-02-22

    tags: analysis, code, programming/php, quality, static, web

    [ permalink ]
24. Misconceptions about testing (and what we should do about them) 2015-02-22

    tags: bug, framework/django, programming/python, programming/testing, quality, unit

    [ permalink ]
25. Python unit testing frameworks: Nose, Pytest 2015-02-13

    tags: code, coverage, feature, nose, programming/python, programming/python/pytest, programming/testing, quality, unit

    [ permalink ]

    Python's built-in unittest module is quite cool, but a bit limited and way too verbose (read: it's quite not easy to incite developers to write unit tests)

    I'm currently looking for more dev-friendly solutions, the key points being:

    • writing test code should be easy and straight-forward -keep the focus on "what to test" instead of "how to transcribe a process to a test"
    • parallelization! -we, spoiled developers, should make good use of our way-too-many-cores build machines...
    • complete feature set!
      • we don't want to just run tests...
      • coverage reports (find dead/weak/untested code sections)
      • output formatting (JUnit-XML seems to be quite a common format out there)

    There seem to be 3 solutions in Python:

    • stock unittest + project-dependent customizations / test helpers
    • nosetests
    • py.test

    And 2 ways of gettings things done:

    • keeping things stock: no external dependency, project-specific implementation...
    • using a test framework: one more module in your (test) virtualenv, more concise tests, more features (// run, code coverage, etc.)

    Some links:

    • http://stackoverflow.com/questions/22856638/nose-vs-pytest-what-are-the-subjective-differences-that-should-make-me-pick
    • http://helixyte.org/2014/04/unit-testing-adventures-moving-from-nose-to-pytest/
    • http://lists.idyll.org/pipermail/testing-in-python/2013-August/005624.html
26. Python: run specific unit tests 2015-02-13

    tags: bug, code, programming/functional-programming, programming/python, programming/testing, quality, unit

    [ permalink ]

    Given your unittests are in the tests directory:

     1# run a specific test module
     2python -m unittest tests.<module>
     3 
     4# run a specific test suite
     5python -m unittest tests.<module>.<class>
     6 
     7# run a specific test
     8python -m unittest tests.<module>.<class>.<test>
     9 
    10# run tests matching a given pattern
    11python -m unittest discover -s tests -p <pattern>