Testing Tour #2: Pairing with Lisa Crispin: Contributing to Gherkin open source documentation

-
Duration: 60 mins

My second session with Lisa Crispin turned out to be a strong style pairing session as each of us 
assumed the driver/navigator role.
Lisa was already working on adding better documentation on explaining declarative vs imperative style 
of Gherkin. Am a complete noob with regard to Cucumber/Gherkin and Lisa was briefly explained 
the what/how behind it. Her PR was already in progress and she needed help navigating via IntelliJ 
and git commands which I was familiar with.
Based on my understanding: Cucumber is a testing tool that supports behavior driven development. 
BDD is a way for software teams to close the gap between business and technical people. It defines 
application behavior using simple English text defined by a language called Gherkin. 

Cucumber was initially implemented in Ruby and then extended to Java framework and it supports 
JUnit as well. All the stakeholders: developers, product managers, QEs, project managers, etc. 
brainstorm as to which test scenarios are required to ensure that the application is successful. 
All these test scripts are in simple English as it serves as good documentation as well. 

Let’s take an example of user authentication, the following can be valid test scenarios:

  • The user should be able to login with valid username and password.
  • The user should not be able to login with invalid username and password. 
  • The user should not be able to login with valid username and invalid password.

      The above test scenario uses declarative style of communication. Lisa explained that this is easier to 
      maintain and less brittle. It only describes the behavior of the application rather than the implementation
      details. 

      Whereas an example of imperative style applied for the same example would look like this:

        The above example requires maintenance as the values are subject to change anytime. Hence it is 
        brittle. 

        Lisa, in her PR was giving a similar example and explaining the 2 different styles of gherkin 
        documentation. Soon her PR was ready to be committed, pushed to the remote branch and ready for 
        review. 

        Thank you Lisa for pairing with me! Had an awesome learning session! Hugs! :)

        Comments

        Post a Comment

        Popular posts from this blog

        Testing Tour #3: Exploring API testing with Maaret Pyhäjärvi

        -
        I had a 60 min session with Maaret where we initially discussed my goal for this session - which was  to explore any open source API and write unit tests. Given Maaret comes with extensive experience,  she suggested to start simple using the Gilded Rose Kata for our session.  She already had the project setup on her laptop, so when we paired via zoom, we were able to  switch control to write tests on her IDE. The first 20-25 mins, we spent trying to understand the  requirements outlined here .  Introduction : Gilded Rose is an inn in a prominent city where they buy and sell goods.  Our task is to test this system based on the rules laid out.These were the basic ground rules: All items have a SellIn value which denotes the number of days we have to sell the item All items have a Quality value denoting how valuable it is At the end of each day, our system lowers both values for each item There were more rules concerning each type of item - which is where it gets inter
        Read more

        Testing Tour #6: Accessibility Testing with Viv Richards!

        -
        Image
          This year has definitely been a rollercoaster ride and I wanted to have small victories to signify that I have been resilient during  times of distress. One of those was to wrap up my testing tour which I had happily kickstarted in the beginning of the year!  Huge thanks to Viv, for agreeing to be on my testing tour and ending the year on a high note! Cheers! :) Viv and I took the role of driver and navigator interchangeably, which led to a wonderful pairing and learning session. We discussed  and played around with the chrome lens plugin and MAC OSX inbuilt voiceover capability.  Chrome lens plugin Viv explained to me about the power of chrome lens plugin - ChromeLens is a set of developer tools that allow developers to code  websites better suited for the visually impaired. The three tools that are currently available are: Filters to experience a website as a blind or colorblind person. Scanners to audit the accessibility readiness of a website.  Trackers to visually show the path
        Read more

        Book Review: Leading Quality + Meeting notes by Tristan Lombard

        -
        Image
          Leading Quality is one of the best pragmatic books I have come across, similar to another book titled “Team Topologies”.  Authors Ronald Cummings and Owais Peer have compiled and categorized the book into 3 different sections catering to audiences  from different backgrounds.    Here are my insights from the book : The original SDLC process mimicked the lean manufacturing and kaizen principles.  Lean manufacturing evolved into total quality management principles that focused on providing value to the customer.  One of my favorite quotes from the book: Continuous deployment without quality is just delivering continuous  bugs to your customer.   The 3 C’s are key to successful implementation of quality: customer issues lead to company issues which eventually  impact your career.  Connect the work of your quality teams to business outcomes.  Section I outlines how one can become a leader of quality by defining the quality narrative.  Audience : This section is crucial for someone starti
        Read more