Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
RailsConf 2017: Building Rails ActionDispatch::SystemTestCase Framework by Eileen M. Uchitelle At the 2014 RailsConf DHH declared system testing would be added to Rails. Three years later, Rails 5.1 makes good on that promise by introducing a new testing framework: ActionDispatch::SystemTestCase. The feature brings system testing to Rails with zero application configuration by adding Capybara integration. After a demonstration of the new framework, we'll walk through what's uniquely involved with building OSS features & how the architecture follows the Rails Doctrine. We'll take a rare look at what it takes to build a major feature for Rails, including goals, design decisions, & roadblocks.
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In her presentation from RailsConf 2017, Eileen Uchitelle discusses the introduction of the new system testing framework, ActionDispatch::SystemTestCase, in Rails 5.1. This framework incorporates Capybara to support system testing with no initial configuration, fulfilling a promise made by DHH in 2014. Key points from her talk include: - **Overview of System Testing**: System tests assess how various components of an application function together as a cohesive whole, going beyond unit testing. - **Integration with Capybara**: Rails 5.1 automatically includes Capybara and sets up the Selenium driver for Chrome, simplifying the process for new applications without extra configuration. - **Implementation Challenges**: The evolution of system testing took three years due to delays in enhancing integration test performance and the volunteer nature of Rails development, which lacks a strict roadmap. - **Process and Decision Making**: Eileen shares her approach, guided by the Rails Doctrine, emphasizing programmer happiness, progress over stability, and community collaboration. - **Technical Benefits**: The new framework supports automatic screenshots on test failure, removes the need for additional dependencies like Database Cleaner, and ensures tests are easier for beginners through visible execution in a browser. - **Open Source Dynamics**: She highlights the challenges of implementing open-source features, such as managing diverse stakeholder opinions and handling public scrutiny, while maintaining the integrity of the project. - **Community Contributions**: The successful merger of the feature involved input from various contributors, showcasing how collaborative development leads to improvements. Eileen concludes by encouraging attendees to participate in open-source contributions, emphasizing that the Rails community's future depends on such engagements. This new testing framework exemplifies the ability to streamline the testing process within Rails applications, making it more accessible and efficient for developers.
Suggest modifications
Cancel
