Test-driven development: atdd instance details

Acceptance Test-driven development: atdd instance details

Author of basic information: Markus Gartner Translator: Zhang Shaopeng Feng Shang Publishing House: People's post and telecommunications Publishing House ISBN: 9787115310620 Release Date: April 2013 Release Date: 16 release page: 146 release: 1-1 category: Computer> Software Engineering and software methodology> Software Quality, software testing and maintenance more about "Acceptance Test-driven development: description of the atdd instance Description: computer books use the acceptance test-driven development (atdd). Business staff, testers, and developers can collaborate to generate testable requirements, help teams build high-quality software more quickly. However, many practitioners still have misunderstandings about atdd. "Atdd by example" is the first entry-level practice guide for successful implementation and application of atdd. Markus Gartner, a pioneer in atdd, will teach readers how to derive the right software system from business personnel, and implement fully automated functional testing that accurately reflects business needs and helps improve development efficiency. Through two end-to-end case studies, Gartner demonstrated how to use different frameworks and languages to implement atdd. Each case involves a large number of actual outputs, including test automation, step definition, and complete case implementation. These examples vividly illustrate the basic principles of atdd, demonstrate how atdd is integrated into the development process, give important tips from Gartner's extensive experience, and point out the dangerous traps to avoid. Readers will learn the following: Understanding the successful implementation of atdd thinking process; using cucumber to use atdd to describe the software that can be understood by business personnel; using atdd tool to test web pages; using fitnesse, a wiki-based acceptance testing framework, atdd is taken to Java; software requirements are collaboratively produced through a new form of discussion; more user-friendly and collaborative automated testing is achieved; test the results more cleanly, listen to the test results, and rebuild the test with value-driven. If you are a tester, analyst, programmer, or project manager, Acceptance Test-driven development: the detailed description of atdd instances ensures that you get real benefits from atdd immediately-and you will get more value as your actual experience increases. Directory Acceptance Test-driven development: atdd instance details Chapter 1 parking lot of the airport Chapter 1 parking fee calculator seminar 1st valet parking 1.1 temporary parking 1.2 economic parking and long-term parking 1.3 Basic instances 1.4 Summary Chapter 2 valet parking testing automation 1.5 the first test case 2.2 is paired to complete the first test 2.2.1 initialize 2.2.2 Check Result 2.3 Table-based test 2.4 Summary chapter 3rd automation of remaining parking lots instances 3.1 Temporary Parking 3.2 Economic parking 3.3 summary chapter 4th expectations and collaboration 4.1 Demand seminar 4.2 subjective expectation Way of Thinking 4.3 collaboration 4.4 summary part 2 Traffic lights Software System Chapter 1 start 5th traffic lights 5.1 fitnesse5.3 support code 5.2 Summary Chapter 2 Traffic lights status 5.4 status requirements 6th first test 6.3 go deep into code 6.4 refactoring 6.4.1 package 6.4.2 lightstate enumeration 6.4.3 edit lightstate6.5 summary chapter 1 requirements of intersection 7th controller 7.1 Implementation of driver controller 7.2 summary chapter 2 discovery and exploration 7.3 discovery field 8.2 drive product code 8.3 Test your bond code 8.4 bond code value 8.5 summary part 3 Acceptance Test-driven development principles Chapter 9th use instance 9.1 use the appropriate format 9.1.1 behavior-driven development 9.1.2 table Format 9.1.3 keyword-driven automation 9.1.4 bonding code and support code 9.1.5 correct format 9.2 refined instance 9.2.1 field test 9.2.2 Boundary Value 9.2.3 pairing test 9.3 cut instance 9.4 consideration missing 9.5 conclusion Chapter 10th collaboration requirements identification 10.1 insights 3 powers 10.2 seminars 10.2.1 participants 10.2.2 goals 10.2.3 frequency and duration 10.3 capturing requirements 10.4 summary chapter 11th text-based automation 11.1 use friendly automation 11.2 automation collaboration 11.3 discovery areas 11.4 summary 12th chapter clean testing 12.1 testing automated development 12.2 listener testing voice 12.3 refactoring testing 12.3.1 extraction variable 12.3.2 extraction keyword 12.4 summary chapter 13th successful use of atdd appendix A cucumbera.1 feature document A.2 step definitions A.3 product code appendix B fitnesseb.1 wiki structure B .2 slim table B .3 support code Appendix C robot frameworkc.1 section C.2 library code this book information source: china Interactive publishing network