Library Hours
Monday to Friday: 9 a.m. to 9 p.m.
Saturday: 9 a.m. to 5 p.m.
Sunday: 1 p.m. to 9 p.m.
Naper Blvd. 1 p.m. to 5 p.m.

LEADER 00000cam a22004457i 4500 
003    OCoLC 
005    20240129213017.0 
006    m     o  d         
007    cr cnu|||unuuu 
008    230524s2023    enka    o     001 0 eng d 
029 1  AU@|b000074864360 
035    (OCoLC)1379845335 
037    9781837638260|bO'Reilly Media 
040    ORMDA|beng|erda|epn|cORMDA|dEBLCP|dOCLCQ 
049    INap 
082 04 005.3 
082 04 005.3|223/eng/20230524 
099    eBook O'Reilly for Public Libraries 
100 1  Bischoff, Benjamin,|eauthor. 
245 10 Writing API tests with Karate :|benhance your API testing 
       for improved security and performance /|cBenjamin Bischoff
       ; foreword by Peter Thomas.|h[O'Reilly electronic 
       resources] 
246 3  Writing application program interfaces with Karate 
250    1st edition. 
264  1 Birmingham, UK :|bPackt Publishing Ltd.,|c2023. 
300    1 online resource (326 pages) :|billustrations 
336    text|btxt|2rdacontent 
337    computer|bc|2rdamedia 
338    online resource|bcr|2rdacarrier 
500    Includes index. 
505 0  Cover -- Title Page -- Copyright and Credits -- Foreword -
       - Contributors -- About the reviewer -- Table of Contents 
       -- Preface -- Part 1:Karate Basics -- Chapter 1: 
       Introducing Karate's Core Concepts -- Technical 
       requirements -- What makes Karate stand out? -- 
       Discovering Karate's strong points -- Core features -- BDD
       versus Karate -- What is BDD? -- Glue code -- The Karate 
       way -- Supported data types in Karate -- JSON -- GraphQL -
       - XML -- YAML -- CSV -- Other text-based formats -- Binary
       formats -- The JavaScript engine -- Java interoperability 
       -- Summary 
505 8  Chapter 2: Setting up Your Karate Project -- Technical 
       requirements -- Installing Java -- Setting the JAVA_HOME 
       environment variable -- Getting to know Karate standalone 
       -- Preparing the IDE -- Setting up Visual Studio Code -- 
       Setting up IntelliJ IDEA -- Importing the example project 
       -- Setting up Karate projects with Maven -- What is Maven?
       -- Installing Maven -- Adding Maven to the PATH variable -
       - Setting up a Karate project with the Maven archetype -- 
       The roles of the different Karate project files -- Summary
       -- Chapter 3: Writing Basic Karate Tests -- Technical 
       requirements 
505 8  Exploring the API under test -- The JSONPlaceholder API --
       Creating a new Karate project -- Adding a new feature file
       -- Configuring test runs -- Adding a scenario -- Calling 
       endpoints and setting parameters -- Setting a URL -- 
       Specifying the HTTP method -- Separating the base URL from
       the path -- Setting query parameters -- Matching status 
       codes and responses -- Matching the status code and type -
       - Making the test fail -- Using assertions and matchers on
       the response -- Exploring the response variable -- 
       Handling nested JSON elements -- Asserting the number of 
       elements with the length property 
505 8  Using matchers -- Making requests with payloads -- Using 
       variables and data tables -- Using variables -- Using data
       tables -- Using a set -- Summary -- Chapter 4: Running 
       Karate Tests -- Technical requirements -- Running and 
       debugging Karate tests through the IDE -- Running via 
       CodeLens and the Karate CLI -- Debugging via CodeLens and 
       Karate standalone -- Using the debug server -- Running 
       tests with Maven -- Understanding Karate runners -- 
       Running tests against different environments -- Using a 
       custom property in a feature file -- Using Karate's 
       environment property -- Setting up karate-config.js 
505 8  Running specific tests -- Running specific runner class 
       methods -- Running specific scenarios -- Filtering tests 
       by tags -- Summary -- Chapter 5: Reporting and Logging -- 
       Technical requirements -- Configuring log options -- 
       Understanding log levels -- Changing the log level -- 
       Suppressing print -- Using Karate's built-in reports -- 
       The different report pages -- Preserving old reports -- 
       Deciding what to report -- Configuring third-party report 
       libraries -- Setting the appropriate Karate options -- 
       Using Cluecumber as a Maven plugin -- Technical 
       requirements 
520    Software in recent years is moving away from centralized 
       systems and monoliths to smaller, scalable components that
       communicate with each other through APIs. Testing these 
       communication interfaces is becoming increasingly 
       important to ensure the security, performance, and 
       extensibility of the software. A powerful tool to achieve 
       safe and robust applications is Karate, an easy-to-use, 
       and powerful software testing framework. In this book, 
       you'll work with different modules of karate to get 
       tailored solutions for modern test challenges. You'll be 
       exploring interface testing, UI testing as well as 
       performance testing. By the end of this book, you'll be 
       able to use the Karate framework in your software 
       development lifecycle to make your APIs and applications 
       robust and trustworthy. 
590    O'Reilly|bO'Reilly Online Learning: Academic/Public 
       Library Edition 
650  0 Application program interfaces (Computer software)
       |xTesting. 
700 1  Thomas, Peter,|ewriter of foreword. 
856 40 |uhttps://ezproxy.naperville-lib.org/login?url=https://
       learning.oreilly.com/library/view/~/9781837638260/?ar
       |zAvailable on O'Reilly for Public Libraries 
938    ProQuest Ebook Central|bEBLB|nEBL30973277 
994    92|bJFN