Agreed on the "helpful" note. According to guidelines it's ideal for documentation not to make references to what "should" come in the future. Instead, we're supposed to stick with what we're documenting in the present moment.

Note for docs team: when this becomes a PR, we'll need to remove this note and sweep for any other future-related notes in there.

@kapunahelewong can I take this issue

Yes, @ajitsinghkaler, thank you!! Please let me know if you need help with any of the issues you've volunteered for. 🌟

A couple of references, @ajitsinghkaler:

• Testing routed Angular components with the RouterTestingModule
• Testing Angular routing components with the RouterTestingModule

The alert seems to be directly related to the preceding paragraph:

A different battery of tests can explore whether the application navigates as expected in the presence of conditions that influence guards such as whether the user is authenticated and authorized.

What's the scope for this issue? Adding a guide for different types of tests using the RouterTestingModule or only integration tests exercising conditions affected by route guards?

Good questions, @LayZeeDK. These are exactly the kinds of questions we are discussing with in the docs team as we rework a lot of the documentation. Do you have any particular thoughts on the scope and types of example tests that you'd be interested in? If you search for something regarding testing what are the topics that first come to mind? Your use cases would also be interesting to hear. If you or others would like to log your thoughts here in this issue I'd be happy to link to this issue from the Jira as context for the writer.

Different types of tests involving the RouterTestingModule:

• Testing routed components
• Testing routing components
• Testing route guards
• Testing route resolvers
• Integration testing routed feature modules
• Integration testing routed feature modules with route guards
• Integration testing a routed component with nested routes
• Integration testing a routed component with route resolvers

I've been intensively looking into this 3 year old issue for the past week:
#15779

I feel more and more convinced that for the most part we don't need to extend our testing APIs to close it, but rather write a guide covering the types of tests listed above.

Thank you, @LayZeeDK! I've added this and #15779 to the Jira work item so the writer who works on it can refer back for context.

Docs team: See https://angular-team.atlassian.net/browse/DOCS-784