uses a "Given, When, Then" syntax. An example of a Given, When, Then scenario is
shown below in Figure 1.
Figure 1: A sample Given, When, Then scenario that shows a transaction at an ATM.
Generally, the team works on these examples when talking about a feature for the
application before it's built. They'll usually write scenarios to describe the different use
cases of a feature into one feature file and have separate feature files for different
features of an application. In HipTest, this functionality is provided by allowing you to
create folders and subfolders for organizing your scenarios. These scenarios will be
executed by a person or, more likely, automation that will run the automation code
against the application being developed to determine if the behaviors are "behaving"
as expected.
When writing scenarios, each step in the scenario is separate so that you can reuse
these steps in different scenarios, reducing duplication of both effort and code. Each of
these steps will eventually become a separate function or method in the automation
code that gets generated so there is reduced duplicate code as well. Figure 2 and 3
show the sample code that gets generated by HipTest.
