EmbeddingGemma 2: an open, lightweight multimodal embedding model
deepmind.google·6d ago
AI Engineering
Lobsters·Jul 27·5 min read
How to Deal with 1,000 Failing Specs in a Rails App (2019)
TL;DR
Upgrading a large Rails application revealed 1,000 failing RSpec tests, prompting a structured approach to resolve issues. The key outcome was a systematic method for addressing test failures during major upgrades.
✦ Why It Matters
Adopt a structured approach to manage and resolve test failures during software upgrades.
Key Takeaways
- Break down errors into manageable chunks for efficient resolution.
- Focus on fixing specs with similar error messages first.
- Document successful fixes to aid future upgrades.
- Understand the root causes of failures from version changes.
Full Summary
A Rails app upgrade from version 2.1 to 3.0 resulted in 8,000 failing RSpec tests out of over 9,000. To tackle this, the author recommends breaking down the errors into manageable chunks, starting with those that share similar messages.
Strategies include fixing related specs together and documenting successful fixes for future reference. The process emphasizes the importance of understanding the root causes of failures, which can stem from changes in Ruby, Rails, or gem versions.
By following these strategies, the author successfully reduced the number of failing specs and improved overall morale during the upgrade process.