VirtualTam's bookmarks

1. Python Coverage could be fast | David R. MacIver 2017-09-26

   tags: coverage, performance, programming/python, programming/python/pytest, programming/testing

   [ permalink ]
2. Why Most Unit Testing is Waste - Python Testing 2017-05-22

   tags: agile, coverage, design, development, programming/object-oriented-programming, programming/python, programming/testing, unit

   [ permalink ]

   • http://www.rbcs-us.com/documents/Why-Most-Unit-Testing-is-Waste.pdf
   • http://www.rbcs-us.com/documents/Segue.pdf
   • https://news.ycombinator.com/item?id=7353767
   • https://www.reddit.com/r/programming/comments/1zqjk8/why_most_unit_testing_is_waste/
   • https://henrikwarne.com/2014/09/04/a-response-to-why-most-unit-testing-is-waste/
3. [CMake] Using gcov/lcov and valgrind with cmake 2016-11-16

   tags: cmake, coverage, memory, programming/c, programming/c++, valgrind

   [ permalink ]
4. 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
5. Cobertura - Jenkins Plugin 2015-01-04

   tags: code, continuous-integration, continuous-integration/jenkins, coverage, programming/python

   [ permalink ]

   DIsplay code coverage stats

6. 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

7. 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/

8. Python bad practice, a concrete case 2014-11-14

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

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

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

   [ permalink ]