VirtualTam's bookmarks

21. Obey the testing goat... 2015-05-10

    tags: continuous-integration, development, driven, framework/django, goat, programming/functional-programming, programming/test-driven-development, programming/testing, unit

    [ permalink ]

    • Test first! Test first!
22. TaskBuster Django tutorial 2015-05-10

    tags: development, framework/django, programming/python, programming/testing, unit, web

    [ permalink ]
23. Tox: a generic virtualenv management and test command line tool 2015-04-28

    tags: development, programming/python, programming/python/virtualenv, programming/testing, unit

    [ permalink ]

    https://bitbucket.org/hpk42/tox

24. PHP - Testing your privates 2015-03-17

    tags: method, private, programming/php, programming/testing, protected, unit

    [ permalink ]

    How to test a private or protected method with PHPUnit?

    see also: https://sebastian-bergmann.de/archives/881-Testing-Your-Privates.html

25. United Diversity - Library 2015-03-15

    tags: architecture, building, culture, ecology, nature, open-source, permaculture

    [ permalink ]

    A collection of misc. resources: FLOSS, ecology, architecture...

26. Misconceptions about testing (and what we should do about them) 2015-02-22

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

    [ permalink ]
27. 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
28. 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>
    

29. python-measurement 2015-01-06

    tags: measurement, observability/metrics, programming/python, system, unit

    [ permalink ]

    https://github.com/coddingtonbear/python-measurement

30. nose: python testing helper 2015-01-04

    tags: continuous-integration, continuous-integration/jenkins, coverage, parallel, programming/python, programming/testing, unit

    [ permalink ]

    Includes support for Coverage, Xunit and other cool stuff ;-) Oh, and there is parallel testing, too \o/

    nosetests --with-coverage --cover-erase --cover-tests --cover-html --cover-html-dir=htmlcov --with-xunit --xunit-file=unit.xml

    via http://www.alexconrad.org/2011/10/jenkins-and-python.html

31. Continuous integration in Python 2014-11-27

    tags: automation, continuous-integration, continuous-integration/travis, development, programming/python, programming/python/pytest, programming/testing, source-code-management/git, unit

    [ permalink ]

    http://ilovesymposia.com/2014/10/01/continuous-integration-0-automated-tests-with-pytest/ http://ilovesymposia.com/2014/10/02/continuous-integration-1-test-coverage/ http://ilovesymposia.com/2014/10/13/continuous-integration-in-python-3-set-up-your-test-configuration-files/ http://ilovesymposia.com/2014/10/15/continuous-integration-in-python-4-set-up-travis-ci/ http://ilovesymposia.com/2014/10/15/continuous-integration-in-python-5-report-test-coverage-using-coveralls/ http://ilovesymposia.com/2014/10/17/continuous-integration-in-python-6-show-off-your-work/ http://ilovesymposia.com/2014/10/27/continuous-integration-in-python-7-some-helper-tools-and-final-thoughts/

32. CI is hard! « Jacob Kaplan-Moss 2014-11-24

    tags: buildbot, continuous-integration, continuous-integration/jenkins, development, framework/django, programming/python, programming/testing, unit, web

    [ permalink ]

    http://jacobian.org/writing/ci-is-hard/ http://jacobian.org/writing/configuration-and-architecture/ https://github.com/jacobian-archive/django-buildmaster

33. A Guide to Testing in Django - Toast Driven 2014-11-24

    tags: development, driven, framework/django, programming/python, programming/testing, unit, web

    [ permalink ]

    https://docs.djangoproject.com/en/1.7/intro/tutorial05/ http://toastdriven.com/blog/2011/apr/10/guide-to-testing-in-django/ http://toastdriven.com/blog/2011/apr/17/guide-to-testing-in-django-2/

34. Is Unit Testing worth the effort? - Stack Overflow 2014-11-24

    tags: continuous-integration, development, driven, programming/testing, unit

    [ permalink ]

    Awesome thread! The topvoted comments show extremely good - yet simple - reasons to become a unit test maniac ;-)

    See also:

    • http://www.c2.com/cgi/wiki?ContinuousIntegration
    • http://www.c2.com/cgi/wiki?UnitTest
35. Test-Driven Development with Python 2014-11-21

    tags: development, programming/python, programming/testing, unit

    [ permalink ]
36. Python bad practice, a concrete case 2014-11-14

    tags: bad, coverage, development, good, hack, pep8, practice, programming/python, programming/testing, unit

    [ permalink ]
37. Un gros guide bien gras sur les tests unitaires en Python, partie 3 | Sam & Max 2014-10-20

    tags: continuous-integration, development, programming/python, programming/testing, unit

    [ permalink ]
38. Python - Code coverage 2014-09-01

    tags: code, coverage, development, programming/python, programming/testing, unit

    [ permalink ]
39. unit testing - Python unittests in Jenkins? - Stack Overflow 2014-08-04

    tags: continuous-integration, continuous-integration/jenkins, junit, programming/python, programming/testing, unit

    [ permalink ]
40. Les joies du code - quand le stagiaire me dit qu'il a fait tous les tests en seulement 15 minutes 2014-06-12

    tags: code, development, programming/testing, trainee, unit

    [ permalink ]