What could be worse than having no tests?
Found a cool package on Laravel News? But how do you know if it's actually worth installing?
In the latest episode of the No Compromises podcast, we discuss what we look for when evaluating third-party packages before bringing them into a project.
Aaron makes the case that what he finds in the tests folder is essentially a deal-breaker: no tests means no trust, but leaving default example tests behind is somehow even worse. Tests reveal whether the maintainer thought through edge cases and serve as living documentation when the README falls short.
We also cover the other signals we weigh: GitHub stars, download counts, issue responsiveness, and how quickly maintainers keep up with new Laravel versions.
Want to work with us on your project?
In the latest episode of the No Compromises podcast, we discuss what we look for when evaluating third-party packages before bringing them into a project.
Aaron makes the case that what he finds in the tests folder is essentially a deal-breaker: no tests means no trust, but leaving default example tests behind is somehow even worse. Tests reveal whether the maintainer thought through edge cases and serve as living documentation when the README falls short.
We also cover the other signals we weigh: GitHub stars, download counts, issue responsiveness, and how quickly maintainers keep up with new Laravel versions.
- (00:00) - Evaluating packages you stumble across
- (01:30) - Why leftover example tests frustrate Aaron
- (03:45) - Tests as documentation and edge case proof
- (05:00) - Checking issues and Laravel version history
- (08:00) - Silly bit
Want to work with us on your project?
