kaleidoscope

In  previous post  we had an overview of the Cucumber, Gherkin & feature file. Now let's see how to write test cases in feature files using Gherkin. Anatomy of a feature-file All non-blank lines in a  feature file  have to start with a valid  Gherkin keyword.  Some of them we discussed in the previous post. Here is the description of the main Gherkin keywords. Feature: The first Keyword in feature-file must be  Feature,  it must be followed by   : After  Feature:  cucumber ignores all the text and lines for processing until a line starting with either  Scenario ,  Background,  or  Scenario Outline  keyword is found. All the text in between is used only for reporting purposes.  The first line is used as the feature name, and the remaining lines (if present) are used as feature descriptions. Scenario: Scenario keyword must also be followed by  :  .  Any text after  :  in this ...

In the  last post , we discussed  git internals  to understand Git. In this post we will discuss Git commands, to use Git. I recommend reading the last post, to easily understand the terminologies used here. I’m going to skip the commands to install git as it varies based on the operating system and y. Once you have our machine architecture. After installation following are the commonly used commands. 1. Check Git Version git —-version   check and confirm the installation 2. Configure Git You can use the below command to set global configurations for Git. git config --global  key “value” . By default, Git doesn’t allow you to commit until it knows who you are. So the first thing to do after installation is, to set the below properties. Preferably globally git config --global   user.name  “My Name” git config --global   user.email  “ myemail@email.com ” NOTE . If your  present working directory  is inside a local git repository, you ...