Talk:Ruby package guidelines
Latest comment: 30 May by Bertptrs in topic Testing gems with outdated dependencies
Testing gems with outdated dependencies
Sometimes it is infeasible to run the tests for a particular gem, as they require older versions of particular gems, which in turn have even more outdated dependencies, leading to a spiraling dependency chain. In such cases, it can be too much to actually run the tests, but it's still useful to run a minimal test on the gem. Simply trying to import the gem and printing some constant can suffice as a smoke test for packaging issues, sussing out missing dependencies and/or rebuilds easily.
I'm not sure whether this should be a tip/trick or whether it shouldn't be mentioned at all, as ideally we do run tests to figure out if our packages works, but I much prefer having this over not having tests.