Shared Examples: it_behaves_like vs include_examples context limits

RSpec provides two primary methods for applying shared examples to a test suite: it_behaves_like and include_examples. While both facilitate test reuse, they differ in how they handle the execution context and the resulting output in the documentation formatter.

The goal is to maintain a clean test hierarchy while ensuring that shared tests have access to the necessary let declarations and before hooks defined in the host spec. There is uncertainty regarding how include_examples handles variable scoping compared to the nested group created by it_behaves_like, particularly when shared examples rely on implicit dependencies from the parent context.

• How does the lack of a nested group in include_examples affect the resolution of let variables defined in the shared block versus the host spec?
• What are the specific implications for failure traceability in the RSpec formatter when using include_examples for a large set of shared tests?