Talks
Speakers
Events
Topics
Search
Sign in
Search
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
search talks for
⏎
Suggest modification to this talk
Title
Description
When you write tests, you are the first user of your code's design. Like any user experience, you may encounter friction. Stubbing endless methods to get to green. Fixing unrelated spec files after a minor change. Rather than push on, let this tedium guide you toward better object-oriented code. With examples in RSpec, this talk will cover testing headaches familiar to any Rails developer. Join me in learning how to listen to your symptoms, diagnose the cause, and find the right treatment. You'll leave with newfound inspiration to write clear, maintainable tests in peace. Your future self will thank you! https://www.wnb-rb.dev/meetups/2024/05/28
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 the talk titled "So writing tests feels painful. What now?", Stephanie Minn addresses the common struggles developers face when writing tests for their code, particularly in Ruby on Rails environments. The main theme revolves around using the challenges of writing tests as indicators for improving code design and reducing testing friction. Through her presentation, Minn highlights several key points: - **Stages of Change Model**: She introduces this model to describe how individuals progress through phases when dealing with complicated tasks, such as writing tests. - **Common Testing Struggles**: Minn acknowledges that many developers encounter testing pain, particularly in complex codebases, where tests can become overwhelming and difficult to manage. - **Observing Reactions**: She emphasizes the importance of being attuned to one's feelings while writing tests, an indicator of potential design issues within the code. - **Writing for Clarity**: Minn discusses the significance of writing tests that not only validate functionality but also serve as documentation for future users, including oneself. - **Code Smells and Refactoring**: The talk covers identifying 'code smells'—issues that hint at deeper design flaws—and how these can be tackled through careful refactoring practices. - **Practical Example**: Using a fictional application 'Patreon for Pets', she walks through a scenario of adding a notification feature to subscription trials, demonstrating the testing process with RSpec. - **Testing Techniques**: Minn illustrates various testing strategies, including the Arrange-Act-Assert pattern, and highlights the significance of maintaining manageable coupling within tests. - **Refactoring for Improvement**: She urges developers to take incremental steps towards refactoring without overwhelming themselves, advocating for the value of clarity and understanding in both code and tests. The conclusion of her talk emphasizes that recognizing and addressing test pain is crucial for long-term maintainability and developer satisfaction. By engaging with the processes surrounding testing, developers can foster a culture of clear and maintainable code. Minn encourages her audience to embrace these concepts and maintain an ongoing dialogue about improving their coding practices.
Suggest modifications
Cancel
