|
|
|
|
LEADER |
00000cam a2200000Ia 4500 |
001 |
OR_ocn773204686 |
003 |
OCoLC |
005 |
20231017213018.0 |
006 |
m o d |
007 |
cr unu|||||||| |
008 |
120118s2012 xx ab ob 000 0 eng d |
010 |
|
|
|a 2011052354
|
040 |
|
|
|a UMI
|b eng
|e pn
|c UMI
|d COO
|d DEBSZ
|d OCLCQ
|d VT2
|d OCLCQ
|d YDX
|d OCLCQ
|d OCLCO
|d OCLCF
|d CEF
|d WYU
|d AU@
|d CNCEN
|d OCLCQ
|d RDF
|d OCLCQ
|d OCLCO
|
019 |
|
|
|a 1065984195
|a 1103261809
|a 1129356101
|
020 |
|
|
|a 0321803027
|
020 |
|
|
|a 9780321803023
|
020 |
|
|
|z 9780321803023
|
029 |
1 |
|
|a DEBSZ
|b 370595165
|
029 |
1 |
|
|a GBVCP
|b 78543576X
|
035 |
|
|
|a (OCoLC)773204686
|z (OCoLC)1065984195
|z (OCoLC)1103261809
|z (OCoLC)1129356101
|
037 |
|
|
|a CL0500000122
|b Safari Books Online
|
043 |
|
|
|a n-us---
|
050 |
|
4 |
|a QA76.76.T48
|b W58 2012
|
082 |
0 |
4 |
|a 004.67820287
|
049 |
|
|
|a UAMI
|
100 |
1 |
|
|a Whittaker, James A.
|
245 |
1 |
0 |
|a How Google tests software /
|c James A. Whittaker, Jason Arbon and Jeff Carollo.
|
260 |
|
|
|a [Place of publication not identified] :
|b Addison-Wesley Professional,
|c ©2012.
|
300 |
|
|
|a 1 online resource (1 volume) :
|b illustrations, maps
|
336 |
|
|
|a text
|b txt
|2 rdacontent
|
337 |
|
|
|a computer
|b c
|2 rdamedia
|
338 |
|
|
|a online resource
|b cr
|2 rdacarrier
|
504 |
|
|
|a Includes bibliographical references.
|
505 |
0 |
|
|a Introduction to Google software testing -- The software engineer in test -- The test engineer -- The test engineering manager -- Improving how Google tests software.
|
520 |
|
|
|a 2012 Jolt Award finalist! Pioneering the Future of Software Test Do you need to get it right, too? Then, learn from Google . Legendary testing expert James Whittaker, until recently a Google testing leader, and two top Google experts reveal exactly how Google tests software, offering brand-new best practices you can use even if you're not quite Google's size ... yet! Breakthrough Techniques You Can Actually Use Discover 100% practical, amazingly scalable techniques for analyzing risk and planning tests ... thinking like real users ... implementing exploratory, black box, white box, and acceptance testing ... getting usable feedback ... tracking issues ... choosing and creating tools ... testing "Docs & Mocks," interfaces, classes, modules, libraries, binaries, services, and infrastructure ... reviewing code and refactoring ... using test hooks, presubmit scripts, queues, continuous builds, and more. With these techniques, you can transform testing from a bottleneck into an accelerator -and make your whole organization more productive!
|
590 |
|
|
|a O'Reilly
|b O'Reilly Online Learning: Academic/Public Library Edition
|
610 |
2 |
0 |
|a Google (Firm)
|
610 |
2 |
7 |
|a Google (Firm)
|2 blmlsh
|
610 |
2 |
7 |
|a Google (Firm)
|2 fast
|
650 |
|
0 |
|a Application software
|x Testing.
|
650 |
|
0 |
|a Web services
|x Testing.
|
650 |
|
7 |
|a Application software
|x Testing
|2 fast
|
650 |
|
7 |
|a Engineering & Applied Sciences.
|2 hilcc
|
650 |
|
7 |
|a Computer Science.
|2 hilcc
|
700 |
1 |
|
|a Arbon, James.
|
700 |
1 |
|
|a Carollo, Jeff.
|
776 |
0 |
8 |
|i Print version:
|a Whittaker, James A.
|t How Google tests software.
|d [Place of publication not identified] : Addison-Wesley Professional, ©2012
|w (DLC) 2011052354
|
856 |
4 |
0 |
|u https://learning.oreilly.com/library/view/~/9780132851572/?ar
|z Texto completo (Requiere registro previo con correo institucional)
|
938 |
|
|
|a YBP Library Services
|b YANK
|n 14854712
|
938 |
|
|
|a Askews and Holts Library Services
|b ASKH
|n AH41026673
|
994 |
|
|
|a 92
|b IZTAP
|