Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Rapid Application Development with AWS Amplify

You're reading from   Rapid Application Development with AWS Amplify Full stack web development on Amazon Web Servics

Arrow left icon
Product type Paperback
Published in Jul 2021
Publisher Packt
ISBN-13 9781800207233
Length 344 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Adrian Leung Adrian Leung
Author Profile Icon Adrian Leung
Adrian Leung
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Section 1: Getting Ready
2. Chapter 1: Getting Familiar with the Amplify CLI and Amplify Console FREE CHAPTER 3. Chapter 2: Creating a React App with AmplifyJS and TypeScript 4. Section 2: Building a Photo Sharing App
5. Chapter 3: Pluggable Amplify UI Components 6. Chapter 4: User Management with Amplify Authentication 7. Chapter 5: Creating a Blog Post with Amplify GraphQL 8. Chapter 6: Uploading and Sharing Photos with Amplify Storage 9. Section 3: Production Readiness
10. Chapter 7: Setting Up an Amplify Pipeline 11. Chapter 8: Test Automation with Cypress 12. Chapter 9: Setting Up a Custom Domain Name and the Amplify Admin UI 13. Other Books You May Enjoy

Writing executable User Stories in Gherkin

Writing executable User Stories with Specification by Examples in Gherkin requires some practice. Gherkin is a domain-specific language for creating concrete examples of how a system should interact with the user in plain English, which everyone in the business can understand. The more you practice, the more you will get used to it quickly. So, let's start with a few common scenarios that will help you create a couple of feature files. Remember that each feature file can have multiple scenarios, just like each User Story can have multiple scenarios (also known as Specification by Example or Executable Specification). You can see this variation in the following examples:

  • A simple feature that requires no user input:
    Feature: A short description of the feature
      User story of the feature goes here
        Rule: Business rule goes here
        Description about the business rule
      ...
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
Banner background image