Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Writing API Tests with Karate

You're reading from   Writing API Tests with Karate Enhance your API testing for improved security and performance

Arrow left icon
Product type Paperback
Published in May 2023
Publisher Packt
ISBN-13 9781837638260
Length 326 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Benjamin Bischoff Benjamin Bischoff
Author Profile Icon Benjamin Bischoff
Benjamin Bischoff
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. Part 1:Karate Basics
2. Chapter 1: Introducing Karate’s Core Concepts FREE CHAPTER 3. Chapter 2: Setting up Your Karate Project 4. Chapter 3: Writing Basic Karate Tests 5. Chapter 4: Running Karate Tests 6. Chapter 5: Reporting and Logging 7. Part 2:Advanced Karate Functionalities
8. Chapter 6: More Advanced Karate Features 9. Chapter 7: Customizing and Optimizing Karate Tests 10. Chapter 8: Karate in Docker and CI/CD pipelines 11. Chapter 9: Karate UI for Browser Testing 12. Chapter 10: Performance Testing with Karate Gatling 13. Index 14. Other Books You May Enjoy

Writing a basic Chrome scenario

Karate’s documentation recommends starting with automating the Chrome browser since it is the easiest and most capable. So, we will now create our first basic browser test for Chrome.

Opening a website in Chrome

We need to know in advance which browser we want to use so that we can specify the correct driver. Based on this, Karate will use the desired browser and protocol. For this example, we will start with the most straightforward one: Chrome.

Configuring the Karate driver

We will create a new scenario called First test and gradually add functionality during the next sections:

Scenario: First test
    * configure driver = { type: 'chrome' }

As with other Karate-specific settings we have seen in earlier chapters, we use the configure keyword. This time, we tell Karate that our driver instance should be of type chrome. This driver instance should not be confused with WebDriver from the W3C WebDriver...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime