Skip to main contentdfsdf

    • Good-enough automation frees the team to deliver high-quality code frequently. It provides a framework that lets the team maximize its velocity while maintaining a high standard.
    • Agile teams focus on always having working software, which enables them to release production-ready software as often as needed. Achieving this goal requires constant testing.

    15 more annotations...

    • Chapter 13 Why We Want to Automate Tests and What Holds Us Back

    58 more annotations...

    • Chapter 14 An Agile Test Automation Strategy

    26 more annotations...

    • Write a test. Think about how you would like the operation in your mind to appear in your code. You are writing a story. Invent the interface you wish you had. Include all of the elements in the story that you imagine will be necessary to calculate the right answers.
    • If the clean, simple solution is obvious but it will take you a minute, then make a note of it and get back to the main problem, which is getting the bar green in seconds.

    22 more annotations...

      • My goal is for you to see the rhythm of Test-Driven Development (TDD), which can be summed up as follows.

        1. Quickly add a test.

        2. Run all tests and see the new one fail.

        3. Make a little change.

        4. Run all tests and see them all succeed.

        5. Refactor to remove duplication.

      • The surprises are likely to include

        • How each test can cover a small increment of functionality

        • How small and ugly the changes can be to make the new tests run

        • How often the tests are run

        • How many teensy-weensy steps make up the refactorings

    • The Litany of Benefits
    • 5. Test Driven Development

    12 more annotations...

1 - 8 of 8
20 items/page
List Comments (0)