VirtualTam's bookmarks
44 bookmarks found
-
LaTeX / Beamer / Minted
2017-04-11 Code / minted / listings
- http://ftp.math.purdue.edu/mirrors/ctan.org/macros/latex/contrib/minted/minted.pdf
- https://tex.stackexchange.com/questions/236706/undefined-control-sequence-with-minted
- https://tex.stackexchange.com/questions/103141/set-global-options-for-inputminted
- https://github.com/gpoore/minted/issues/125
Minted formatting
- https://tex.stackexchange.com/questions/85932/mintedinconsolata-straight-quotes
- https://tex.stackexchange.com/questions/5443/use-another-monospaced-font
- http://www.tug.dk/FontCatalogue/sourcecodepro/
Columns
- https://tex.stackexchange.com/questions/32931/multiple-columns-with-images-and-wrapped-text-in-beamer
- https://tex.stackexchange.com/questions/1858/stable-vertical-alignment-of-columns-in-beamer
Icons / images
- FA - https://tex.stackexchange.com/questions/165150/how-to-use-fontawesome-icons-in-latex-with-moderncv
- FA - https://tex.stackexchange.com/questions/338657/how-to-include-socials-icons-like-github-and-linkedin-in-moderncv
- SVG - https://tex.stackexchange.com/questions/2099/how-to-include-svg-diagrams-in-latex
- SVG - https://tex.stackexchange.com/questions/122871/include-svg-images-with-the-svg-package
Overlay / Pause / step-by-step
- https://tex.stackexchange.com/questions/26987/show-a-frame-step-by-step
- https://tex.stackexchange.com/questions/117887/how-to-insert-overlays-in-latex-beamer
Titles
URL
-
Python unit testing frameworks: Nose, Pytest
2015-02-13 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:
-
xkcd: ISO 8601
2013-08-19 Formatting dates...