The article demonstrates how a fintech loan‑risk system applied shift‑left testing—embedding quality checks from requirements through design and development—to identify 87% of logic defects early, reduce P0 incidents to zero, cut UAT time by 40%, and establish measurable quality metrics.
The article examines why shift‑left testing is now a practical necessity, compares five mainstream tools—SonarQube, ESLint + Jest + Cypress, Swagger/Pact, Cucumber, and Testim.io—across scenarios, integration depth, learning curve and ROI, and provides a decision framework backed by real‑world case studies.
This article details a practical transformation from manual to automated testing using Jest and BDD‑generated HTA, explaining the challenges, technical solutions, mock‑data management, pipeline integration, and measurable results such as higher coverage, lower development cost, and faster release cycles.
This article explains how Behavior‑Driven Development (BDD) translates business requirements into shared, natural‑language scenarios, improves collaboration among product, development, and testing teams, and provides concrete steps, tool choices, and code examples to implement BDD effectively in real projects.
This article explores how to build highly extensible test automation frameworks by applying proven design patterns such as modular architecture, Page Object Model, data-driven testing, BDD, keyword-driven testing, parallel execution, abstraction layers, and plug-in components, while addressing current challenges and future AI-driven evolution.
This article presents ten actionable recommendations—including using layered abstractions, prioritizing testability, running tests frequently in CI, adhering to the test pyramid, adopting Page Object and BDD patterns, understanding AI, selecting appropriate tools, and investing in training—to dramatically improve the effectiveness and maintainability of automated testing in software projects.
Behavior‑Driven Development (BDD) is an agile methodology that uses natural‑language Gherkin scenarios to describe system behavior, fostering collaboration among developers, testers, and product owners, with detailed examples, best practices, and tool recommendations for implementing BDD across various software projects.
This article outlines seven practical unit‑test naming patterns, explains their structure with real‑world code examples, compares their advantages and drawbacks, and offers guidance on selecting the most suitable convention for different project sizes and team workflows.
This article outlines ten essential practices for testers in agile projects, covering early requirement involvement, test strategy creation, CI/CD integration, collaboration, TDD/BDD adoption, exploratory and performance testing, regression, continuous improvement, and knowledge sharing to ensure high‑quality software delivery.
The article explains how to transform abstract software requirements into executable specifications using scenario‑based BDD, outlines story‑granularity practices, describes a requirement‑instantiation workshop, and details automated verification techniques to improve DevOps efficiency and software quality.
Test‑Driven Development (TDD) and Behavior‑Driven Development (BDD) are software development approaches that start with writing tests or user stories, outlining core steps, advantages, disadvantages, and offering guidance on selecting the appropriate method based on project requirements, team expertise, and business communication needs.
This article provides a detailed guide on user stories in agile project management, covering definitions, characteristics, benefits, differences from traditional requirements, writing techniques like the INVEST principle and BDD format, common pitfalls, and best practices such as workshops, continuous feedback, and collaboration with development teams.
This article explains the concepts of Test‑Driven Development (TDD), Unit Test‑Driven Development (UTDD), Acceptance Test‑Driven Development (ATDD) and Behavior‑Driven Development (BDD), discusses why TDD is not dead, compares the three approaches, and provides a step‑by‑step Java implementation with code samples, testing workflow, and refactoring guidance.
Discover how Kahlan, a full‑featured BDD testing framework for PHP, enhances unit and integration testing with RSpec‑style syntax, built‑in code coverage, powerful stubbing, monkey‑patching, and flexible reporting, all without requiring PECL extensions.
This article compares two E2E test case generation approaches—recording via Playwright’s codegen and behavior‑driven development (BDD) using Gherkin—detailing their principles, code examples, selector handling, DSL design, and the trade‑offs in flexibility, difficulty, and readability for web testing.
This article explains the core concepts, rhythms, and practical applications of Test‑Driven Development (TDD) and Behavior‑Driven Development (BDD), illustrating how the red‑green‑refactor loop and business‑focused scenarios improve code quality, design, and collaboration between developers and stakeholders.
This article provides a comprehensive overview of Agile methodology, detailing how testing adapts to Agile practices, comparing Scrum and Kanban, and exploring testing techniques such as BDD, ATDD, exploratory testing, and session‑based testing, while offering guidance for aligning testing with Agile delivery.
The team combats outdated documentation and costly front‑end maintenance by treating unit tests for the use‑case layer as living documentation, using BDD‑style Given‑When‑Then tests that assert only observable behavior, which improves code readability, eases onboarding, and provides a reliable safety net for future changes.
This article explains software testing fundamentals, classifies test methods, outlines general testing principles, dives into front‑end testing types and popular frameworks, provides code snippets for a minimal test runner, and compares TDD and BDD approaches, offering a comprehensive guide for developers.
Test‑Driven Development (TDD) flips the traditional coding workflow by writing failing tests first, then code to pass them, enabling safer design changes, higher internal quality, and seamless integration with ATDD/BDD to ensure delivered software meets user requirements.
Flybirds is a BDD‑based, open‑source UI automation framework for mobile apps that provides a plug‑in architecture, CLI scaffolding, multilingual support, rich reporting, and seamless integration with CI pipelines, enabling developers to write natural‑language feature files and run them on Android and iOS devices.
The article presents a comprehensive guide to using the Spock testing framework for Java and Groovy backend development, illustrating its BDD‑style DSL, data‑driven tables, integrated mocking (including static methods via PowerMock), exception verification, in‑memory DAO testing, and enhanced coverage reporting compared to JUnit.
This article explores why unit testing is essential, how to conquer the psychological obstacles that prevent developers from writing tests, and provides practical methodologies such as TDD, BDD, the test pyramid, and the Fixture‑Scenario‑Case pattern with concrete Java examples.
This article presents practical Selenium automation best practices—including early and frequent testing, BDD adoption, proper wait strategies, reporting, PageObject usage, automatic screenshots, test design, and mindful tool reliance—to help engineers achieve stable, efficient web test suites.
This article explains how unit testing goes beyond coverage metrics, showing that writing testable code improves design, performance, and robustness, and provides practical guidance on refactoring, mock usage, data‑driven tests, TDD, BDD, and agile development practices.
This article explains how Ctrip's vacation team introduced behavior‑driven development (BDD) for UI automation testing using Cucumber and Puppeteer, covering the testing background, BDD concepts, framework selection, project structure, CI/CD integration, parallel execution, and best practices such as test‑id usage to improve reliability.
The article describes how Ctrip Ticket's front‑end team introduced Behavior‑Driven Development (BDD) using Cucumber and the Macaca‑based MEC framework to unify requirements, automate testing, reduce manual effort, and achieve over 90% UI test coverage while cutting integration costs by 75%.
This article provides a detailed tutorial on Cucumber‑JVM, covering its BDD concepts, Gherkin syntax, feature file structure, step definition implementation, tagging strategies, command‑line execution, and Maven/IDEA project setup for Android mobile testing.
This article provides a detailed tutorial on using Cucumber-JVM for Android SDK automated testing, covering framework basics, Gherkin syntax, step definitions, parameter handling, tag usage, Maven setup, and execution methods with code examples.
This article walks through creating a lightweight Mocha‑like testing framework in JavaScript, covering BDD‑style APIs, directory layout, suite and test class design, hook handling, asynchronous support, a runner that traverses the suite‑test tree, and a reporter that outputs test results.
This article examines common misconceptions and mistakes in implementing Agile and DevOps—such as misusing Scrum, overly long daily stand‑ups, indiscriminate automation testing, superficial CI pipelines, and ineffective Kanban—while offering concrete, principle‑driven practices to achieve efficient, high‑quality software delivery.
This article guides you through setting up Behat for PHP, showing how to install the tool, write feature files, configure build targets, implement step definitions, and run comprehensive integration tests to dramatically improve code quality.
User stories are essential for agile development and continuous delivery, and this article explains why they matter, contrasts them with traditional waterfall requirements, and provides a detailed, step‑by‑step template—including examples and acceptance criteria—to help teams transition smoothly from legacy requirement documents to effective, deliverable user stories.
This article explains the fundamentals of unit testing, including its importance, various test types, tool categories, implementation principles, hooks, best‑practice guidelines, and introduces the Jest JavaScript testing framework with installation steps, features, and example test scripts for both synchronous and asynchronous code.
To cut costly manual testing for Meituan‑Dianping’s overseas travel apps, the team replaced Calabash with an Appium‑Cucumber BDD framework, gaining cross‑platform stability, easier iOS integration, richer element locating, Jenkins‑compatible reporting, and faster overall execution despite slightly longer per‑run times.
This article explains why test cases are essential for high‑quality, maintainable code, compares TDD and BDD agile models, and introduces key frontend testing tools such as Mocha, Should.js, Nock, Istanbul, and mochawesome with practical usage examples.
This guide explains why test cases are essential, compares TDD and BDD agile approaches, and introduces key frontend testing tools—including Mocha for test suites, Should for assertions, Nock for HTTP mocking, and Istanbul for coverage—while providing code examples and best‑practice recommendations for writing maintainable, high‑quality tests.
Front‑end developer Xiao Ming discovers how unit testing with TDD/BDD, Mocha, and various assertion libraries can ensure reliable Node.js deployments, prevent regressions, and enable confident refactoring, while also learning to measure coverage with Istanbul.
This article analyzes the benefits and drawbacks of Cucumber and RobotFramework through multiple real‑world case studies, compares their features in detailed tables, and proposes practical principles for choosing the most suitable automated testing framework based on project requirements and team skills.
