https://github.com/MovingBlocks/Terasology http://jenkins.terasology.org/
VirtualTam's bookmarks
-
2015-03-15 -
2015-03-15 -
2015-03-14 Common ops & clauses:
- CREATE TABLE - https://www.sqlite.org/lang_createtable.html
- ALTER TABLE - https://www.sqlite.org/lang_altertable.html
- UPDATE - https://www.sqlite.org/lang_update.html
-
2015-03-12 - PSR-1 Basic Coding Standard - http://www.php-fig.org/psr/psr-1/
- PSR-2 Coding Style Guide - http://www.php-fig.org/psr/psr-2/
-
2015-03-10 kbd converts a human-readable chord to a key sequence
-
2015-03-08 -
2015-03-03 -
2015-03-02 -
2015-03-02 -
2015-02-27 -
2015-02-22 -
2015-02-14 -
2015-02-13 Beware! Very cool book dealing with Lisp programming, with plenty of examples
-
2015-02-13 Programming... Do you speak it?
-
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: