Test Driven Development
(Difference between revisions)
(pulled over from google doc) |
(Explanation and info from Nick Ingalls) |
||
| Line 15: | Line 15: | ||
** Kent Beck - extreme programming (ford motor) | ** Kent Beck - extreme programming (ford motor) | ||
** http://foss2serve.org/index.php/Test_Coverage_Activity | ** http://foss2serve.org/index.php/Test_Coverage_Activity | ||
| + | |||
| + | * Info that Nick Ingalls gave me | ||
| + | ** https://gist.github.com/ingalls/70508ec69c8e97a1c81e pseudo-code TDD | ||
| + | ** https://github.com/substack/tape tape tap-producing test harness for node and browsers | ||
Revision as of 16:15, 16 February 2016
TDD
- Idea 1: Find a project that already has a testing harness and associated tests; learn it, and add a new unit test
- Idea 2: Create a test harness to make, build, and run unit tests on an existing open source project
- Jim Bowring has done this in the past, though it seems they are lengthy projects vs a shorter activity; Do we want to create a “project”-oriented LA?
- Teach the “mental discipline” of testing
- How can we test a Requirement?
- Ensuring testing starts at user requirement gathering
- Iterating through tests once code has been written, helps to improve the tests
- Dave thinks ManageIQ does unit testing
- Background reading:
- http://www.cs.cofc.edu/~bowring/ - course in testing
- Boris Byser - the test guru
- Kent Beck - extreme programming (ford motor)
- http://foss2serve.org/index.php/Test_Coverage_Activity
- Info that Nick Ingalls gave me
- https://gist.github.com/ingalls/70508ec69c8e97a1c81e pseudo-code TDD
- https://github.com/substack/tape tape tap-producing test harness for node and browsers
