teamcapybara/capybara

Capybara is a browser automation and integration testing framework for web applications. It provides a unified API for interacting with web pages, supporting multiple headless and browser-based drivers including Selenium, RackTest, and Chrome, Firefox, Safari, and Edge. The system enables developers to write acceptance tests that simulate user interactions, verify page content, and manage browser state across different test frameworks like RSpec, Minitest, and Cucumber.

This period marks the Capybara 3.0 release, characterized by a comprehensive architectural refactor that renamed the project from 'webcat' to 'capybara' and introduced a modular driver and node interface. The team modernized the build system with RSpec and Cucumber, removed legacy drivers and scripts, and significantly expanded the test suite to cover headless browser automation and session interactions.

16 changes

This period focused on deepening Capybara's integration with Cucumber and RSpec, introducing new DSLs, step definitions, and comprehensive test coverage. Concurrently, the codebase underwent significant architectural refactoring, including modularizing the RackTest and Selenium drivers and restructuring internal query resolution logic to support modern browser features and dependency versions.

11 changes

This period focused on a comprehensive refactoring of the Capybara codebase, particularly the Selenium driver and selector architecture. The work introduced modular browser-specific modules, restructured selector and filter classes for better maintainability, and added support for Minitest expectations and advanced node interactions like drag-and-drop and scrolling.

12 changes

This period focused on improving code maintainability by refactoring the Capybara codebase, splitting monolithic registration and selector definition files into modular components. Concurrently, the team addressed specific behavioral issues, including improved visibility detection for popovers and form elements, and fixed a blocking issue in Puma's SSL socket handling.

4 changes

teamcapybara/capybara was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.