integration-testing

End-to-end browser UI testing with Capybara verifies UI states through actual clicks, form submissions, and state transitions rather than synthetic script shortcuts. This approach ensures the UI behaves correctly under real user scenarios by simulating genuine end-to-end browser paths.

To minimize Selenium overhead, structure tests with concise, comprehensive examples that cover full feature flows end-to-end. This optimized example structure reduces the number of individual browser interactions needed while maintaining thorough verification of JavaScript-driven components and UI states.

Integration test files for JavaScript-driven components and full feature flows should be placed in the `spec/integration/` directory and `spec/components/**/*_system_spec.rb` directories. These locations systematize end-to-end browser UI testing within the project's existing framework structure.

Yes, Selenium and Capybara are utilized for automated UI verification of JavaScript-driven components and full feature flows. This Skill systematizes end-to-end browser UI testing, applying real-user path-based testing strategies to verify state transitions, clicks, and form submissions.

Real user testing with Capybara complements the project's existing testing frameworks and best practices by focusing on real-user interactions over synthetic tests. It integrates seamlessly with current practices while adding thorough verification of UI interactions and states.