This common question during BDD coaching sessions doesn’t always have a straightforward answer as team experience and processes influence the best approach
We are searching for senior software developers to join the Behave Pro Cloud development team. Our values are important to us, they are key to our success and they also make Hindsight a great place to work
Here, we break down how you can solve the issue of who should take ownership of tests, based on the features of Cucumber acceptance tests and Behave Pro.
BDD often gets confused with TDD - this blog post explores the reasons why and how this can be avoided, while looking at useful test driven development tools.
Exploring what scenario outlines are, when to use them and how to create them within Behave Pro.
The decision follows Atlassian’s announcement of Hipchat end of life.
A look into the talks Mark plans to go to at Agile2018.
This seamless and secure integration between GitHub and Jira makes collaboration easier than ever.
Useful techniques to reveal alternative ideas during collaborative sessions.
We will be running a workshop at Agile 2018 in San Diego on Thursday, August 9th from 9:00am-10:15am.
Effective techniques to delve deeper into ideas during collaborative sessions
How to get started using different questioning techniques during collaborative sessions
With many tools and languages available, what steps can you take to choose and implement a BDD framework into your project?
The fourth and final article in our series, this post looks into the anti-pattern that automated scenarios are enough test coverage.
Dealing with legacy systems often means a lack of documentation, but BDD addresses this challenge and helps teams successfully implement system updates.
The third in our series, this post looks into the anti-pattern of documenting all acceptance criteria as individual scenarios.
BDD often gets confused with ATDD (acceptance test driven development) - this blog post explores the reasons why and how this can be avoided.
In this blog from the series on BDD anti-patterns we explore why using scenarios as test cases isn't good practice, and how to resolve it.
Challenges in BDD implementation can arise from anti-patterns taking hold, such as when the agile team lacks direction in collaborative sessions, but solutions are not out of reach.
Forwood Safety specialize in online management systems for high-risk industries, here describes how Behave Pro for Jira has become one of the backbones of their product development process.
Step by step guide to setting up and running a basic Selenium WebDriver test, including important changes since version 3 release.
Cucumber is a great tool for creating living documentation within BDD using test automation techniques, but sometimes using it is not ideal or cost-effective.
Step by step guide to setting up Cucumber-JVM project to run in IntelliJ IDE and via Maven.
Step-by-step setup so you can run it inside your Eclipse IDE as well as via Maven.
Debriefing completed exploratory test sessions - why it is important, who is involved, and how to ensure the debrief is effective and valuable.
Leveraging BDD in a test strategy, and solving test problems that BDD was never designed to solve
How to create test charters and build tests, uncovering bugs, creating useful test notes and knowing when to stop testing - this summary helps you get started with exploratory testing.
Understanding outside-in development to ensure development is guided by what the business wants as opposed to delivering testing.
The value of feature files can extend beyond being a tool for discussion and collaboration, and help us to identify a wide range of exploratory testing activities that we want to execute.
Understanding the distinction between a user story and feature file allows teams to build a healthy library of feature files detailing key product behaviours.