| Tag |
First Indicator |
Second Indicator |
Subfields |
| LEADER |
00000uam a2200000 a 4500 |
| 001 |
in00004249366 |
| 005 |
20260122221107.1 |
| 006 |
m o d |
| 007 |
cr cn |
| 008 |
080513s2010 xx o eng |
| 020 |
|
|
|z 9780321719478
|
| 020 |
|
|
|z 0321714083
|
| 020 |
|
|
|z 9780321714084
|
| 020 |
|
|
|z 0321719476
|
| 035 |
|
|
|a (CaSebORM)9780321719478
|
| 040 |
|
|
|d UtOrBLW
|
| 041 |
0 |
|
|a eng
|
| 100 |
1 |
|
|a Pugh, Ken,
|e author.
|0 http://id.loc.gov/authorities/names/no2007120295
|
| 245 |
1 |
0 |
|a Lean-Agile Acceptance Test-Driven Development :
|b Better Software Through Collaboration /
|c Pugh, Ken.
|
| 250 |
|
|
|a 1st edition.
|
| 264 |
|
1 |
|b Addison-Wesley Professional,
|c 2010.
|
| 300 |
|
|
|a 1 online resource (368 pages)
|
| 336 |
|
|
|a text
|b txt
|2 rdacontent
|
| 337 |
|
|
|a computer
|b c
|2 rdamedia
|
| 338 |
|
|
|a online resource
|b cr
|2 rdacarrier
|
| 347 |
|
|
|a text file
|
| 520 |
|
|
|a In Acceptance Test Driven Development (ATDD), developers work with customers and testers to create acceptance tests that thoroughly describe how software should work from the customer's viewpoint. By tightening the links between customers and agile teams, ATDD can significantly improve both software quality and developer productivity. This is the firststart-to-finish, real-world guide to ATDD for every agile project participant. Leading agile consultant Kenneth Houston Pugh begins with a dialogue among a developer, tester, and customer, explaining the "what, why, where, when, and how" of ATDD and illuminating the experience of participating in it. Next, Pugh presents a practical, complete reference to each facet of ATDD, from creating simple tests to evaluating their results. He concludes with five diverse case studies, each identifying a realistic set of problems and challenges, together with proven solutions. Coverage includes How to develop software with fully testable requirements How to simplify and componentize tests and use them to identify missing logic How to test user interfaces, service implementations, and other elements of a software system How to identify requirements that are best handled outside software How to present test results, evaluate them, and use them to assess overall progress How to build acceptance tests that serve development organizations, not just customers How to scale ATDD to even the largest projects
|
| 533 |
|
|
|a Electronic reproduction.
|b Boston, MA :
|c Safari,
|n Available via World Wide Web.
|d 2011.
|
| 538 |
|
|
|a Mode of access: World Wide Web.
|
| 542 |
|
|
|f Copyright © 2011 Pearson Education, Inc.
|g 2011
|
| 588 |
|
|
|a Online resource; Title from title page (viewed December 22, 2010)
|
| 500 |
|
|
|a Electronic resource.
|
| 655 |
|
7 |
|a Electronic books.
|2 local
|
| 710 |
2 |
|
|a Safari, an O'Reilly Media Company.
|
| 856 |
4 |
0 |
|u https://proxy.library.tamu.edu/login?url=https://go.oreilly.com/TAMU/library/view/-/9780321719478/?ar
|z Connect to this electronic resource
|t 0
|
| 999 |
f |
f |
|s f21dada9-522b-3636-8633-d33fd4ce93ce
|i 3dac56be-57d2-3808-8ce3-8fbd144df11f
|t 0
|
| 952 |
f |
f |
|a Texas A&M University
|b College Station
|c Electronic Resources
|s www_evans
|d Available Online
|t 0
|h No information provided
|
| 998 |
f |
f |
|t 0
|l Available Online
|