This is an old revision of the document!
The more you invest in quality, the less time it takes to develop working software.
Quality is not just testing
Trying to improve the quality of software by doing more testing is like trying to lose weight by weighing yourself more often. (Steve McConnell)
Quality is:
This lecture looks at basic things every developer can do to maintain quality.
o Then you move on to the second function…
A unit test exercises one component in isolation
An integration test exercises the whole system
Regression testing is the practice of rerunning tests to check that the code still works
Any test can have one of three outcomes:
o Don't know anything about the system being tested
A specification is something that tells you how to classify a test's result
How to write tests so that:
A test consists of a fixture, an action, and an expected result
o A fixture is something that a test is run on o Can be as simple as a single value, or as complex as a networked database
Every test should be independent
o I.e., the outcome of one test shouldn't depend on what happened in another test o Otherwise, faults in early tests can distort the results of later ones
So each test:
o Creates a fresh instance of the fixture o Performs the operation o Checks and records the result
Find the exercises at http://software-carpentry.org/3_0/qa.html