Terms Flashcards
Test First
When should you write your tests? Before you write the code that is to be tested
Test List
List over all the test you will have to code. Add to it when new tests are discovered
One Step Test
Which test should you pick from the next? Pick a test that will teach you something and that you are confident you can implement.
Isolated Test
The test should affect each other at all
Evident Tests
By writing the test code evident, readable, and as simple as possible we avoid writing defective tests
Fake it (Till you make it)
Once you have a broken test, make it return the constant you want it to. Once your test is running, gradually transform it
Triangulation
Abstract only when you have two or more examples
Assert First
It’s in the title m8
Break
Take break pall
Evident Data
Include expected and actual results in the test itself, and make their relationship apparent. Tests are made for the coder, not the computer
Obvious Implementation
How do you implement simple operations? Just implement them
Representative Data
What data do you use for your tests? Select a small set of data where each element represents a conceptual aspect or a special computational precessing
Automated Test
How do you test your software? Write an automated test
Test Data
What data do you use for test-first tests? Use data that makes the tests easy to read and follow. If there is a difference in the data, then it should be meaningful. If there isn’t a conceptual difference between 1 and 2, use 1
Child Test
How do you get a test case running that turns out to be too big? Write a smaller test case that represents the broken part of the bigger test case. Get the smaller test case running. Reintroduce the larger test case.
