OpKey provides behavior driven development that allows teams to describe software behavior in plain English. Unlike other frameworks, OpKey requires no programming skills and provides test automation and collaboration features. Key aspects of OpKey include writing test cases before development, executing tests with different tools, and self-explanatory results and reports.
1. Your First Step toward Behavior Driven Development with OpKey
OpKey Behavior driven development (BDD) allows software development teams to describe
their Software behavior in plain English. This behavior is written in a business-readable domain-
specific language that works as documents, automated tests and development assistance.
Unlike other BDD Frameworks OpKey provides the overall Test Automation without any
programming and kind of collaboration OpKey provides is available nowhere.
Collaboration between Team members who are writing Features and Automation
components. Feature files and Automation components are made available to all other
members working on the project.
No Programming Skill is required. Unlike other Framework available in market it does not
require any programming skill to write Automation component.
Write Test cases (Scenarios) and acceptance criteria before performing any development.
(TeBeDe -Test Before Development).
Write your story once and execute it with any of the automation tool at backend.
A self explanatory Result and Report. It gives snapshot of DONE Features at a glance.
Test Your Features on 150+ OS-Browser combinations in parallel with OpKey Cloud.
BDD is changing Agile development
Landscape.
OpKey is now 100% BDD enabled.
What is there in OpKey BDD?
Test Automation
was never
that Easy
2. 5 Easy Steps to get started
The Simplest ever BDD experience
Map with
Automation
Component
Configure
Automation
Component
Run
Feature
Self
explanatory
Result
Write Your Features in Plain English
For Ex.
Scenario: Add two numbers
Given I have entered 10 in calculator
And I have entered 15 in calculator
When I press ADD button
Then the result should be 25
Map each step of Scenario with an
Automation component at backend.
Just Right Click on Scenario steps and
auto generate your Automation
component or map these steps with
existing components,
Write Your Automation Component
without programming.
It’s the familiar keyword driven
approach where we just need to select
keywords for each action.
Write
Features
3. With that OpKey gives us a host of other features like:
And Many More…….