kaleidoscope

In our previous post  Behavior Driven Development  we discussed BDD. Here, let's look at  Cucumber.  The flagship BDD framework for java, but not limited to Java. Why Cucumber As we saw in the previous post, until the Automation phase, BDD is all about discovering and formulating  behavioral scenarios  through collaboration. Its the automation phase, where things really happen. It would be easy if we could write these behavioral scenarios in plain English ( or another preferred spoken language ) and runtime could understand and execute those for us. This is where Cucumber comes to the rescue. Cucumber Cucumber is a framework that let us write application-behavioral-expectations in meaningful spoken-language-text using  Gherkin. Cucumber implementations are available in many programming languages as shown below. Courtesy — Cucumber.io supported programming languages NOTE: It's recommended (not mandatory) to choose an implementation for the same platform...

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 ...

N one of the operating systems comes with a preinstalled JDK, including macOS. In this post, let's see how to manually install and manage multiple JDK on macOS. If you are not interested in any explanation, go to the very end of the post for commands. But I’ll recommend reading it. A well-known process for installing any software on macOS is, either clicking an app icon or drag-and-drop the app icon into the Applications folder. This hides all installation details under the fancy app icons and an in-progress bar. However, we developers like to see the logs and play with the command line tools. For this purpose,  Linux Distros  use package managers like  yum  or  apt-get . But as with all things Apple, Most common free software don't work in macOS. This is where  HomeBrew  comes to the rescue HomeBrew As the tool's homepage says, it is The Missing Package Manager for macOS. Homebrew is the easiest and most flexible way to install the UNIX tools Apple d...