Notes On Work - by Caleb Porzio
Who even needs tests
· Summarized
Key takeaways
- Technical debt can accumulate when development speed takes precedence over rigorous testing.
- Different testing tools come with their own advantages and may influence a developer's approach.
- A shift towards manual testing and reducing automated tests can be a valid strategy for some development teams.
- Confidence in code can be built through experience, even without exhaustive testing.
Summary
Confessions of Technical Debt
The podcast opens with the host admitting to accruing technical debt in their project, Flux, due to a lack of comprehensive testing. The host explains how they typically ensure quality by adding tests for new features and bug fixes in their open-source projects, which helps in maintaining confidence in their codebase. However, due to the fast pace of development in Flux, the host has not maintained the same rigorous testing practices, highlighting the challenge of balancing speed and quality.
Testing Tools and Strategies
The host discusses their experience with various testing frameworks such as Playwright, Cypress, and Dusk. They reflect on the benefits and drawbacks of each tool, pointing out that while they appreciate the functionality of Playwright for running tests in parallel and providing detailed error reports, their test suite in Flux has been kept minimal due to resource constraints. The conversation also touches upon the host's evolving approach to testing, influenced by industry leaders like Peter Levels and DHH, who advocate for moving fast and embracing a more cowboy development style.
The Shift Away from Automated Testing
As the episode progresses, the host contemplates whether automated testing is becoming outdated. They note that tests often lead to more complexities and maintenance challenges, prompting a preference for manual testing instead. Drawing on insights from DHH, who has reduced reliance on automated tests due to their brittleness, the host shares their current workflow for handling deployments and addressing issues. They emphasize the importance of being knowledgeable and careful as they navigate potential pitfalls in development.
Future Developments and Confidence in Code
Looking ahead, the host mentions working on a WYSIWYG editor for Flux without writing extensive tests but expressing confidence in its stability. This decision reflects a broader commentary on how developers might adapt their testing strategies based on project needs and the desire to innovate quickly. The host concludes by hinting at exploring this theme further in the next episode, focusing on the future of testing in development.
Follow this show on AudioBrevity and new episodes get summarized for you. Create a free account