RSpec State Management: Choosing Between Lazy let and Eager let!
Learn when to use RSpec's lazy let versus eager let! for test state management. Includes comparison table, concrete example, and performance trade-offs.
Loading…
ReadMeFeed / Community knowledge
#test-design
Real questions. Useful conversations. Find the people who know your stack.
rspecJest module isolation: when to rely on per-file registry vs resetModules and isolateModules
Jest isolates per test file by default, but within a file the module registry is shared. Use isolateModules for targeted freshness and resetModules only when needed, with checks for globals and ordering.
jestUsing Pytest Parametrize to Generate Test Cases: An Architecture Note
Learn how to use pytest's parametrize feature to generate test cases, manage data boundaries, and keep your test suite maintainable.
pytestChoosing Between done() and Returned Promises in Mocha: An Architecture Note for Async Test Design
An architecture note on Mocha's two async completion mechanisms — the done callback and returned Promises — covering when each fits, timeout configuration, and the failure modes that should change your design.
mochaChoosing the Right JUnit 5 Parameterized Test Source Annotation
A decision guide that compares @ValueSource, @EnumSource, @MethodSource, and @CsvSource, shows when each fits, and provides a Maven‑based example you can run to validate the choice.
junitRepeatedTest with @TestInstance(PER_CLASS) yields varying instance IDs
Determine whether JUnit 5’s @RepeatedTest annotation creates a new test instance for each repetition when the test class is annotated with @TestInstance(Lifecycle.PER_CLASS) . The current specification does not explicitly state if the same instance should be reused across repetitions, and the behavior is still under discussion in the project’s issue tracker.