You should all start reading XKCD.
ssh and screen; BLAST.
When we say “testing” we really mean automated testing. The central problems addressed by testing are correctness and reproducibility. (While these are linked, they are not the same!)
There are two basic kinds of tests that I’d like to briefly discuss. One kind of test is a unit test. The other kind of test is a regression test. (There are also many more.)
Unit tests address small units of code, like functions. They are used to isolate and nail down and prove the functionality of potentially complicated little functions.
Regression tests address the overall function of code, and they are used to make sure that your code is doing the same thing today as it was yesterday.
I’ll show you examples of both, but quickly :).
We’re going to be using the nose testing framework, which is just a framework that makes it easy to find and execute tests.
Basically, ‘nose’ creates a command ‘nosetests’ that finds and runs tests. The idea is that you won’t need to register new tests.
A test function looks like this:
def test_something():
# run some code
# fail loudly or succeed silently
(An abbreviated version of: http://ged.msu.edu/angus/git-intro.html)
The purpose of version control is to serve as a method for tacking changes to files, which enables lots of things:
A brief introduction:
This file can be edited directly through the Web. Anyone can update and fix errors in this document with few clicks -- no downloads needed.
For an introduction to the documentation format please see the reST primer.