<record xmlns="http://www.loc.gov/MARC21/slim" xmlns:zs="http://www.loc.gov/zing/srw/">
  <leader>16930nam a2200721 i 4500</leader>
  <controlfield tag="001">almatuudk_9923194914102884</controlfield>
  <controlfield tag="003">DE-602</controlfield>
  <controlfield tag="005">20231214134736.0</controlfield>
  <controlfield tag="006">m     o  d |      </controlfield>
  <controlfield tag="007">cr cnu||||||||</controlfield>
  <controlfield tag="008">231214s2023    enka    o     000 0 eng d</controlfield>
  <datafield tag="020" ind1=" " ind2=" ">
    <subfield code="a">9781837637850</subfield>
  </datafield>
  <datafield tag="020" ind1=" " ind2=" ">
    <subfield code="a">1837637857</subfield>
  </datafield>
  <datafield tag="024" ind1="7" ind2=" ">
    <subfield code="a">10.0000/9781837637850</subfield>
    <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
    <subfield code="a">(MiAaPQ)EBC30984746</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
    <subfield code="a">(Au-PeEL)EBL30984746</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
    <subfield code="a">(OCoLC)1412621269</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
    <subfield code="a">(OCoLC-P)1412621269</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
    <subfield code="a">(CKB)29250279300041</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
    <subfield code="a">(FR-PaCSA)88949676</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
    <subfield code="a">(CaSebORM)9781837638024</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
    <subfield code="a">(DE-B1597)691526</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
    <subfield code="a">(DE-B1597)9781837637850</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
    <subfield code="a">(FRCYB88949676)88949676</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
    <subfield code="a">(DE-B1597)BR1423333</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
    <subfield code="z">(OCoLC)1437998909</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
    <subfield code="a">(OCoLC)1437998909</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
    <subfield code="a">(EXLCZ)9929250279300041</subfield>
  </datafield>
  <datafield tag="040" ind1=" " ind2=" ">
    <subfield code="a">MiAaPQ</subfield>
    <subfield code="b">eng</subfield>
    <subfield code="e">rda</subfield>
    <subfield code="e">pn</subfield>
    <subfield code="c">MiAaPQ</subfield>
    <subfield code="d">MiAaPQ</subfield>
  </datafield>
  <datafield tag="044" ind1=" " ind2=" ">
    <subfield code="a">pl</subfield>
    <subfield code="c">PL</subfield>
  </datafield>
  <datafield tag="049" ind1=" " ind2=" ">
    <subfield code="a">DE-83;9923194914102884</subfield>
  </datafield>
  <datafield tag="050" ind1=" " ind2="4">
    <subfield code="a">QA76</subfield>
    <subfield code="b">.H487 2023</subfield>
  </datafield>
  <datafield tag="072" ind1=" " ind2="7">
    <subfield code="a">COM051330</subfield>
    <subfield code="2">bisacsh</subfield>
  </datafield>
  <datafield tag="082" ind1="0" ind2=" ">
    <subfield code="a">929.605</subfield>
    <subfield code="2">23</subfield>
  </datafield>
  <datafield tag="091" ind1=" " ind2=" ">
    <subfield code="a">DE-83;9923194914102884</subfield>
  </datafield>
  <datafield tag="092" ind1=" " ind2=" ">
    <subfield code="a">almatuudk_9923194914102884</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Heusser, Matthew,</subfield>
    <subfield code="e">author.</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
    <subfield code="a">Software Testing Strategies :</subfield>
    <subfield code="b">A Testing Guide for The 2020s /</subfield>
    <subfield code="c">Matthew Heusser and Michael Larsen.</subfield>
  </datafield>
  <datafield tag="250" ind1=" " ind2=" ">
    <subfield code="a">First edition.</subfield>
  </datafield>
  <datafield tag="264" ind1=" " ind2="1">
    <subfield code="a">Birmingham, England :</subfield>
    <subfield code="b">Packt Publishing Ltd.,</subfield>
    <subfield code="c">[2023]</subfield>
  </datafield>
  <datafield tag="264" ind1=" " ind2="4">
    <subfield code="c">&#169;2023</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">1 online resource (378 pages)</subfield>
  </datafield>
  <datafield tag="336" ind1=" " ind2=" ">
    <subfield code="a">text</subfield>
    <subfield code="b">txt</subfield>
    <subfield code="2">rdacontent</subfield>
  </datafield>
  <datafield tag="337" ind1=" " ind2=" ">
    <subfield code="a">computer</subfield>
    <subfield code="b">c</subfield>
    <subfield code="2">rdamedia</subfield>
  </datafield>
  <datafield tag="338" ind1=" " ind2=" ">
    <subfield code="a">online resource</subfield>
    <subfield code="b">cr</subfield>
    <subfield code="2">rdacarrier</subfield>
  </datafield>
  <datafield tag="500" ind1=" " ind2=" ">
    <subfield code="a">Description based upon print version of record.</subfield>
  </datafield>
  <datafield tag="500" ind1=" " ind2=" ">
    <subfield code="a">Investigating tools for internationalization and localization</subfield>
  </datafield>
  <datafield tag="505" ind1="0" ind2=" ">
    <subfield code="a">Cover -- Title Page -- Copyright -- Dedication -- Contributors -- Table of Contents -- Preface -- Part 1: The Practice  of Software Testing -- Chapter 1: Testing and Designing Tests -- Jumping into testing -- The impossibility of complete testing -- What is the EVP asking for? -- Toward a theory of error -- Testing software - an example -- Testing software - an analysis -- Quick attacks - the airdropped tester -- Test design - input space coverage -- Equivalence classes and boundaries -- Decision tables -- Decision trees -- All-pairs and pairwise testing -- High volume automated approaches -- Other approaches -- Data and predictability - the oracle problem -- Summary -- Further reading -- Chapter 2: Fundamental Issues in Tooling and Automation -- Technical requirements -- No silver bullets - you can't radically fix the test cycle -- The minefield regression problem -- Coverage model -- The Battleships problem - testing versus checking -- Comparing Battleships to bugs -- Automation rarely beats human intuition -- The maintenance problem -- The dangers of comprehensive tests -- The money problem -- Lessons from the fundamental issues -- Summary -- Chapter 3: Programmer-Facing Testing -- Technical requirements -- The programmer's view -- Testing and reliability -- The hexagonal architecture -- Introducing FizzBuzz -- Unit tests -- TDD -- Consequences of TDD -- Unit test and unit code design -- Using test doubles to create seams -- Mutation testing -- Web APIs from a test perspective -- Web API testing strategy -- Testing functional and legacy code -- A Roman Numerals Kata -- Summary -- Chapter 4: Customer-Facing Tests -- Technical requirements -- A word of warning -- Human Or Tooling-is it either/or? -- GUI test automation patterns -- Eliminating redundancy with domain-specific libraries -- Eliminating redundancy through object locators.</subfield>
  </datafield>
  <datafield tag="505" ind1="8" ind2=" ">
    <subfield code="a">Do you need conditionals, looping structures, and variables? -- The tradeoff between assertion and image recognition -- Designing your own system -- Toward specification by example -- Specification by example -- Low-code and no-code test automation -- Batch- and model-driven test automation -- This chapter is completely wrong -- Summary -- Chapter 5: Specialized Testing -- Technical requirements -- Understanding load and performance testing -- Getting to know the basics of load testing -- Setting up a load test -- Exploring security testing -- Security concepts -- Checking out common security vulnerabilities -- Learning about industry standards -- Investigating some security testing tools -- Delving into accessibility testing -- What is accessibility? -- Advocating for accessibility -- Investigating the distinctions between accessibility and inclusive design -- Learning about the WCAG standard -- Investigating some accessibility testing tools -- Internationalization and localization -- Preparing for internationalization and localization -- Investigating tools for internationalization and localization -- CI -- CI and the pipeline -- Getting involved with build management as a tester -- Investigating CI tools -- Regulated testing -- Navigating regulatory requirements -- Summary -- Chapter 6: Testing Related Skills -- Technical requirements -- Finding bugs -- Oracles in software testing -- Inattentional blindness and Oracles -- About the word bug -- Writing bug reports -- Effective bug reports -- Effective reproduction steps -- Planning testing - cases and plans -- Test cases in practice -- Metrics and measurement -- Metric dysfunction -- Project projections -- Influencing change -- Summarizing information -- Summary -- Chapter 7: Test Data Management -- Technical requirements -- The test data problem -- Test data and database apps.</subfield>
  </datafield>
  <datafield tag="505" ind1="8" ind2=" ">
    <subfield code="a">The standard data seed -- Table-driven - when test data drives behavior -- Scriptable users and structure -- Exploring synthetic users -- Leveraging production refreshes -- Exploring development, test, and production environments -- Understanding the regulatory issues in test data management -- The user spy feature -- Summary -- Part 2: Testing and  Software Delivery -- Chapter 8: Delivery Models and Testing -- Technical requirements -- Waterfall -- The advantages of and place for the waterfall -- The V-Model -- Iterative, incremental, and mini waterfalls -- Extreme Programming (XP) -- The context of XP -- Scrum and SAFe -- The context of Scrum -- SAFe and its context -- House-rules software development -- The Agile Manifesto -- Context-driven testing -- Illustrations of the principles in action -- Kanban as a house rule -- Continuous delivery and deployment -- DevOps, Platform Engineering, SRE -- Summary -- Further reading -- Chapter 9: The Puzzle Pieces of Good Testing -- Technical requirements -- Recipes - how to do hard things -- Defining recipes -- Shouldn't recipes just be automated? -- Do recipes overlap with technical documentation? -- Coverage - did we test the right things well enough? -- Precise code coverage measures -- Closing out coverage -- Defects - what is the status of the software? -- Schedule and risk - too many test ideas, not enough time -- Iterative testing -- Strategy - what are our risks and priorities? -- Dashboard - how do we communicate what we know? -- Summary -- Chapter 10: Putting Your  Test Strategy Together -- What are we doing now? -- Getting the form filled out -- The elevator pitch -- A census of risk -- Defining a real risk census -- Setting priorities, time management, and scope -- Today's strategy versus tomorrow's goals -- Summary -- Chapter 11: Lean Software Testing -- Lean software testing defined.</subfield>
  </datafield>
  <datafield tag="505" ind1="8" ind2=" ">
    <subfield code="a">From ideas in practice to the term "Lean" -- The seven wastes -- Waste #1 - transport -- Waste #2 - inventory -- Waste #3 - motion -- Waste #4 - waiting -- Waste #5 - overprocessing -- Waste #6 - overproduction -- Waste #7 - defects -- (New) waste #8 - ability -- Removing waste in testing -- Flow -- Visualizing flow - an example -- Multitasking -- Measurement - lead time versus cycle time -- Efficiency and congestion -- Metric - touch time -- Batch size -- Queues and efficiency -- Arrival time pacing -- Limiting work in progress to create a pull system -- Release cadence -- One-piece flow and CD -- Summary -- Part 3: Practicing  Politics -- Chapter 12: Case Studies and Experience Reports -- RCRCRC at scale -- The 1-day test plan -- RCRCRC in the enterprise -- A coverage dashboard -- Test coverage blinders -- Pair and tri-programming -- Discovering the expertise paradox -- Making expertise transparent -- The evolution of the test strategy -- The alternative to evolution - information hiding -- Professional pushback - dealing with bullies -- Power in the workplace -- One way to say it -- Boundaries in the enterprise -- Narcissistic communication -- Boundary enforcement - the power move -- If you choose to stay -- Summary -- Chapter 13: Testing Activities or a Testing Role? -- Technical requirements -- The cultural conflict with a testing role -- How we got here - the bad news -- How we got here - developing at internet speed -- Building a risk mitigation team -- The purpose of the risk exercise -- Faith-based versus empirical test automation -- The math behind faith-based test automation -- Possible outcomes -- Shift left and shift right -- (Actually) continuous testing -- Summary -- Chapter 14: Philosophy and Ethics in Software Testing -- Philosophy and why it matters in testing -- Sprint Length: it depends -- Shu Ha Ri: learning by osmosis.</subfield>
  </datafield>
  <datafield tag="505" ind1="8" ind2=" ">
    <subfield code="a">A tough question: what do you want? -- Ethics and ethical reasoning in testing -- Ethical frameworks -- Classic ethical challenges -- Practical ethical issues in testing -- Skipping test steps and the good news -- Decisions are not made in meetings -- Scientific thinking and logical fallacies -- Logical fallacies -- How we wind up in hell and how to escape -- Put the responsibility in the right place -- Summary -- Additional readings for the serious philosopher -- Chapter 15: Words and Language About Work -- Context-driven testing and the other schools -- The Agile school -- The DevOps or CD school -- The analytical school -- The factory school -- The quality school -- The context-driven school -- Precise language -- Wordsmatter -- The benefits of being imprecise -- Process versus skill -- Testing and checking -- Yes, we can assure quality -- Summary -- Further reading -- Chapter 16: Testing Strategy Applied -- A mobile test strategy example -- Our sample mobile app -- Designing a test program -- Mobile system coordination and deployment -- The human element -- AI in software testing -- The state of AI tools -- Possible ways to use AI for testing -- Other forms of AI in testing -- The bottom line for AI testing -- A few thoughts to leave with -- Thoughts on documentation -- Summary -- Index -- About PACKT -- Other Books You May Enjoy.</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Unlock the true potential of software testing to achieve seamless software performance with this comprehensive guide Key Features Gain a solid understanding of software testing and master its multifaceted strategies Empower yourself to effectively overcome software testing challenges Develop actionable real-world testing skills for succeeding in any role Purchase of the print or Kindle book includes a free PDF eBook Book Description Software Testing Strategies covers a wide range of topics in the field of software testing, providing practical insights and strategies for professionals at every level. With equal emphasis on theoretical knowledge and practical application, this book is a valuable resource for programmers, testers, and anyone involved in software development. The first part delves into the fundamentals of software testing, teaching you about test design, tooling, and automation. The chapters help you get to grips with specialized testing areas, including security, internationalization, accessibility, and performance. The second part focuses on the integration of testing into the broader software delivery process, exploring different delivery models and puzzle pieces contributing to effective testing. You'll discover how to craft your own test strategies and learn about lean approaches to software testing for optimizing processes. The final part goes beyond technicalities, addressing the broader context of testing. The chapters cover case studies, experience reports, and testing responsibilities, and discuss the philosophy and ethics of software testing. By the end of this book, you'll be equipped to elevate your testing game and ensure software quality, and have an indispensable guide to the ever-evolving landscape of software quality assurance. What you will learn Explore accessibility, functional testing, performance testing, and more as an integral part of testing Find out how to implement a wide range of testing approaches Develop the skills needed to create effective testing strategies tailored to your project's needs Discover how to prioritize and execute the most impactful test ideas Gain insight into when and how to apply different testing elements Defend your chosen testing strategy with a comprehensive understanding of its components Who this book is for This book is for a broad spectrum of professionals engaged in software development, including programmers, testers, and DevOps specialists. Tailored to those who aspire to elevate their testing practices beyond the basics, the book caters to anyone seeking practical insights and strategies to master the nuanced interplay between human intuition and automation. Whether you are a seasoned developer, meticulous tester, or DevOps professional, this comprehensive guide offers a transformative roadmap to become an adept strategist in the dynamic realm of software quality assurance.</subfield>
  </datafield>
  <datafield tag="545" ind1=" " ind2=" ">
    <subfield code="a">Heusser Matthew: Matt Heusser is the Managing Director at Excelon Development, where he specializes in Software Delivery, DevOps, and Testing across diverse industries such as software, fintech, and automotive. With a Master's degree from Grand Valley State University and a remarkable track record, Matt has earned international recognition through awards and delivered keynote speeches that have left lasting impressions. Matt's legacy in the tech world includes pioneering the world's first multi-user distributed spreadsheet, a groundbreaking innovation that predates even Google Sheets. His expertise extends to project rescue initiatives, including one initiated by BMW's board of directors, where he demonstrated his exceptional leadership and problem-solving skills. In addition to his hands-on contributions, Matt has effectively managed API test development teams and provided invaluable support to developers. Matt Heusser's career is a testament to his unwavering commitment to pushing the boundaries of technology, delivering outstanding results, and inspiring the next generation of innovators in the software and technology landscape. Larsen Michael: Over the past decade, Michael has been actively engaged in the realm of software testing, focusing on audits and testing fixes in alignment with U. S. Section 508 and E. U. WCAG accessibility standards. His commitment extends beyond testing, as he is equally passionate about promoting accessibility and inclusive design through talks and training sessions. Michael leverages a diverse set of tools, including Axe, Lighthouse, Wave, VoiceOver, JAWS, NVDA, ColorContrast Analyzer, among others, to facilitate the accessibility testing process. He has played a pivotal role in urging organizations to prioritize accessibility considerations in their software development and testing endeavors. Moreover, Michael possesses a knack for uncovering issues within systems, collaborating with developers to rectify them, and assisting customers in devising innovative solutions. His overarching mission is to nurture and lead top-notch testers and test teams, fostering a culture of excellence in the field. With an extensive career spanning three decades, Michael has lent his expertise to various product domains and industries, encompassing network routers and switches, virtual machines, capacitance touch devices, video games, and a wide spectrum of client/server, distributed database, and web applications. Beyond his software testing endeavors, Michael boasts an impressive array of achievements and affiliations. He holds a Black Belt certification from the Miagi-Do School of Software Testing, co-founded and facilitates the Americas chapter of Weekend Testing, serves as a director for the Association for Software Testing (AST), leads instruction for the Black Box Software Testing courses offered by AST, curates training materials for the SummerQAmp initiative, and currently holds a position on the board of the Pacific Northwest Software Quality Conference (PNSQC).</subfield>
  </datafield>
  <datafield tag="588" ind1=" " ind2=" ">
    <subfield code="a">Description based on print version record.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Computer software</subfield>
    <subfield code="x">Testing.</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
    <subfield code="a">Larsen, Michael,</subfield>
    <subfield code="e">author.</subfield>
  </datafield>
  <datafield tag="776" ind1="0" ind2="8">
    <subfield code="z">ISBN 9781837638024</subfield>
  </datafield>
  <datafield tag="776" ind1="0" ind2="8">
    <subfield code="z">ISBN 1837638020</subfield>
  </datafield>
  <datafield tag="906" ind1=" " ind2=" ">
    <subfield code="a">BOOK</subfield>
  </datafield>
  <datafield tag="338" ind1=" " ind2=" ">
    <subfield code="b">cr</subfield>
  </datafield>
  <datafield tag="924" ind1=" " ind2=" ">
    <subfield code="a">9923194914102884</subfield>
    <subfield code="b">DE-83</subfield>
    <subfield code="c">KOBV</subfield>
    <subfield code="d">c</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
    <subfield code="s">false</subfield>
  </datafield>
</record>