# Cucumber Cucumber is a tool that supports behavior-driven development by reading plain-text executable specifications and validating software behavior. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Cypress Ambassador Spotlight: Javier Flores DevFeed: [Cypress Ambassador Spotlight: Javier Flores]() Original publisher: [Read original article]() Published: 2026-07-16T21:08:08Z Content type: opinion Language: en Sources: [Cypress Blog]() Topics: [Cypress](), [Testing](), [Cucumber](), [Bootcamp](), [selectors](), [debugging](), [Automation]() Tags: [ambassador](), [automation](), [community](), [cypress](), [debugging](), [flaky](), [learning](), [projects](), [selectors](), [testing]() ### AI overview This interview highlights Javier Flores's work as a Cypress Ambassador, QA Automation Lead, mentor, and bootcamp instructor. It discusses practical Cypress testing, Cucumber exercises, interactive time-travel debugging, automatic waiting, deterministic tests, stable selectors, and beginner-friendly end-to-end testing practices. ### Source excerpt What motivates you to be a Cypress Ambassador? I want to help grow a strong, practical testing community around Cypress. I show people working code and let them build confidence by doing. That's the same philosophy behind the bootcamp I run: everyone leaves with their own repo, not just notes. How do you currently help others that are either using Cypress or interested in using Cypress? I mentor teammates and collaborate closely with developers and product owners to improve testing practices ## How we improved reporting and monitoring of test automation results DevFeed: [How we improved reporting and monitoring of test automation results]() Original publisher: [Read original article]() Author: Giuseppe Donati Web Test Automation Engineer Not a stereotypical Italian guy; Except Published: 2023-02-15T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [Testing](), [Test automation](), [GitHub Actions](), [Selenium](), [CI/CD](), [Cloud](), [Kafka](), [elasticsearch](), [kibana](), [logstash](), [Grafana](), [Cucumber]() Tags: [article](), [elasticsearch](), [frontend](), [gcp](), [github-actions](), [grafana](), [kafka](), [kibana](), [logstash](), [monitoring](), [quality-assurance](), [selenium](), [test-automation]() ### AI overview The article describes trivago's updated system for executing, reporting, and monitoring Selenium-based end-to-end tests. It covers GitHub Actions workflows, custom runners on Google Cloud, cloud report storage, Kafka and Logstash processing, Elasticsearch and Kibana visualization, and Grafana and Slack alerting. ### Source excerpt Over the last few years, we completely refactored what was described in our previous article about how we use the ELK sta... ## Leveraging Kotlin for Tests DevFeed: [Leveraging Kotlin for Tests]() Original publisher: [Read original article]() Author: Jossi Wolf Published: 2021-12-01T15:00:03Z Content type: tutorial Language: en Sources: [Stories by Jossi Wolf on Medium]() Topics: [Kotlin](), [Testing](), [Behavior-driven development](), [Cucumber](), [Development]() Tags: [android](), [bdd](), [given-when-then](), [junit](), [kotlin](), [testing](), [tests]() ### AI overview This article explains how Kotlin language features and naming patterns can improve test readability. It covers the Given/When/Then pattern, meaningful test names, and using Kotlin backtick function names to make tests clearer. ### Source excerpt Writing tests can be an important part of developing applications. Whether unit tests, integration tests or others, Kotlin's language features and clever naming patterns can help us increase the readability of tests. The patterns suggested here aren't new or innovative; rather they are more modern adaptions of well-established practices. I learned about these adaptions from my lovely colleague Volodymyr Galandzij who did fantastic work in setting up the testing framework in a codebase we worked on together. Given/When/Then You may have heard of the Given/When/Then pattern -- also known as the Cucumber/Gherkin syntax -- if you have written tests before, or you might even recognize it from Jira tickets. Originally introduced as a part of BDD (Behavior Driven Development), similar patterns like the Four-Phase Test (you'll see some similarities to JUnit here) have existed for a good amount of time. Martin Fowler gives a good small summary of all of this in his article about the Given/When/Then pattern: The essential idea is to break down writing a scenario (or test) into three sections:The given part describes the state of the world before you begin the behavior you're specifying in this scenario. You can think of it as the pre-conditions to the test.The when section is that behavior that you're specifying.Finally the then section describes the changes you expect due to the specified behavior. Regardless of the testing philosophy you follow, there's a good chance that the Given/When/Then pattern can be applied to your tests. But how does this look in practice? I heard that adding a featured image helps increase clicks. Does it work? Who knows! If it does, thank you, Sigmund on Unsplash!Test Names I argue that test names are one of the most important parts of writing good tests. The name of the test should help you understand what the test does. One quality of a good test is that it fails when the actual outcome is different from the expected outcome. When a test fails, it ## Interview for BrowserStack's Breakpoint 2020 Conference DevFeed: [Interview for BrowserStack's Breakpoint 2020 Conference]() Original publisher: [Read original article]() Author: Matthias Endler Published: 2020-07-03T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [Testing](), [Test automation](), [Continuous Delivery (CD)](), [Cucumber](), [Open Source]() Tags: [bdd](), [conference](), [continuous-delivery](), [engineering-culture](), [interview](), [open-source](), [qa](), [release-engineering](), [test-automation](), [testing]() ### AI overview This article announces Benjamin Bischoff's BrowserStack interview and talk for the virtual Breakpoint 2020 testing summit. It introduces his work in test automation at trivago and describes the company's technical and procedural changes toward more efficient continuous delivery. ### Source excerpt After 15 years as a game/application developer and trainer, Benjamin decided to make test automation his career. He's currently a Test Automation Engineer in trivago's core QA team. Benj... ## Acceptance Criteria: From Informal Text to Formal Specifications DevFeed: [Acceptance Criteria: From Informal Text to Formal Specifications]() Original publisher: [Read original article]() Author: Artur Dryomov Published: 2019-01-20T00:00:00Z Content type: opinion Language: en Sources: [Artur Dryomov]() Topics: [Agile](), [Requirements](), [Cucumber](), [Specifications]() Tags: [agile](), [communication](), [requirements](), [specifications]() ### AI overview The article discusses Acceptance Criteria as a communication artifact between business and technical teams. It traces their evolution from informal text and email to formal specifications, highlighting Cucumber's Gherkin syntax as a structured option. ### Source excerpt Cooperation! It sure sounds better than bureaucracy. A released product is a result of cooperation between the Business and the Tech. There is an obvious issue though. Both sides have different mindsets. The misunderstanding is inevitable. How do we solve this? Well, there are still wars on the planet so apparently humanity wasn't able to find a solution. What about establishing not world peace but a good communication channel? Agile methodologies establish such artifact as Acceptance Criteria (AC). AC is a specification for how the product should work. Sounds good and the motivation is solid, but there is a catch -- there are no explicit requirements. AC can consist of memes and be distributed by birds -- the sky is the limit (literally). Let's take a look at the evolution and trace our path to the bureaucracy nirvana. ## Cluecumber Report Maven Plugin for Cucumber test reporting DevFeed: [Cluecumber Report Maven Plugin for Cucumber test reporting]() Original publisher: [Read original article]() Author: Benjamin Bischoff Test Automation Engineer; Author; Speaker; Magician Github Profile Linkedin Profile Published: 2017-11-16T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [Cucumber](), [test](), [Maven](), [Java]() Tags: [css](), [frontend](), [html](), [images](), [java](), [maven](), [maven-plugin](), [monitoring](), [open-source](), [plugin](), [quality-assurance](), [release](), [reporting](), [test]() ### AI overview The article explains why trivago replaced its existing Cucumber reporting Maven plugin and describes the design of the Cluecumber Report Plugin. The new plugin uses HTML templates and generates overview and scenario-detail pages from Cucumber JSON results. ### Source excerpt We were not as happy as we could be with out Cucumber test reporting solution - so we decided to build a new and shiny one from scratch. ## Cucable Maven plugin for parallel execution of Cucumber scenarios DevFeed: [Cucable Maven plugin for parallel execution of Cucumber scenarios]() Original publisher: [Read original article]() Author: Benjamin Bischoff Test Automation Engineer; Author; Speaker; Magician Github Profile Linkedin Profile Published: 2017-06-30T00:00:00Z Content type: tutorial Language: en Sources: [Trivago]() Topics: [Cucumber](), [Maven](), [test](), [Selenium](), [ci]() Tags: [browser](), [ci](), [frontend](), [maven](), [maven-plugin](), [open-source](), [parallel](), [plugin](), [quality-assurance](), [speed](), [test](), [user-experience]() ### AI overview Trivago describes creating Cucable, a Maven plugin that splits Cucumber scenarios into smaller chunks for parallel execution. The article explains limitations of custom runners, tag-based execution, feature-based execution, and existing plugins, particularly for scenario outlines and CI automation. ### Source excerpt Running Cucumber scenarios in parallel can be tricky, especially when a custom test runner is used. That's why we created Cucable - a Maven plugin to split test scenarios into smaller chunks that can be run at the same time. ## Kochiku: CI for long test suites DevFeed: [Kochiku: CI for long test suites]() Original publisher: [Read original article]() Author: Square Engineering Published: 2013-09-06T16:04:00Z Content type: release Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [ci](), [GitHub Actions](), [Rails](), [Ruby](), [Cucumber](), [RSpec](), [Amazon EC2](), [Selenium]() Tags: [build](), [ci](), [continuous-integration](), [ec2](), [engineering](), [rails](), [ruby](), [selenium](), [tests](), [unit-tests]() ### AI overview Square introduces Kochiku, a continuous integration system that partitions long test suites into distributable chunks and runs them through a queue of build workers. ### Source excerpt A new Continuous Integration tool from Square ## Integrating Development and Testing to Improve Software Quality at FINN.no DevFeed: [Integrating Development and Testing to Improve Software Quality at FINN.no]() Original publisher: [Read original article]() Author: vivek Published: 2012-05-07T07:29:20Z Content type: opinion Language: en Sources: [Finn.no]() Topics: [Testing](), [Development](), [Cucumber](), [Code]() Tags: [code-testing](), [development](), [qa](), [quality-assurance](), [regression](), [testing]() ### AI overview The article argues that testing should be integrated into the development process rather than treated as a separate quality assurance department. At FINN, teams without a dedicated QA role reportedly achieved the same quality as teams with QA by sharing responsibilities and using different task-management practices. ### Source excerpt When a developer is finished with a development issue, it must be tested. People often think the goal of testing should be to find all the errors. Well, it's not entirely realistic. Actually, it's impossible! Despite the title of "quality insurance" testers can never really ensure level of quality, nor can they be expected to find all the errors. The real goal of testing should be to improve the software. As at the end of the day we want to minimize the cost of fixing critical bugs after a release, minimize cost of handling customer complaints and pushing a patch in the production. So it is import to understand that Quality Assurance is a process, not a department. Today there are basically two different components of QA role in FINN. One of which is "QA in a team" and the other one is of a "team without the QA". The QA role today is often a safety net for many developers and teams. The role involves manual testing in the sprint, regression testing and writing Cucumber tests. In addition this role has some administrative tasks such as being contact person for the Release Manager, participating in the release status meeting, filling out the checklist of early / late shift, contact for Tech Support (E-journal issues), participating in status meetings at Call Center after release, and verifying the patch to production. Everything that's listed so far is managed also by teams without QA. What we have seen so far, is that a team without QA delivers the same quality as the team with QA in developing an FINN application. Then comes the question, how do they manage to do it? They have the same responsibilities as the "QA in a team", but they have different practices on how they manage the tasks (some have rolling QA role, others have a fixed arrangement but they are NOT dependent on one individual person). If we want to deliver a good quality code, testing must become a central pillar of the development process. When I say the role of QA is dead, but development and testing ## Integration Testing Resque with Cucumber DevFeed: [Integration Testing Resque with Cucumber]() Original publisher: [Read original article]() Author: Square Engineering Published: 2010-08-16T16:00:00Z Content type: tutorial Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [Cucumber](), [Integration testing](), [race-condition](), [Testing](), [Processes](), [Concurrent Programming]() Tags: [asynchronous](), [continuous-integration](), [engineering](), [integration](), [integration-testing](), [process](), [processes](), [queue](), [race-condition](), [testing](), [tests](), [unit-tests]() ### AI overview This article explains how Square integration-tests Resque asynchronous background jobs with Cucumber. It addresses race conditions by forking a Resque worker from the Cucumber process, pausing the worker, and using signal handling to release it, wait for queued jobs to finish, and pause it again. ### Source excerpt Processing asynchronous jobs deterministically