doc: list Testing guides under Best Practices

[bajtos]

I found it weird that our sidebar is listing "Testing your application" at top level, while most of other testing-related content is nested under "Best practices".

This pull request moves "Testing your application" to "Best practices" section and also adds a link to "Testing your extensions" to best practices.

Please consider this change as a quick improvement of the current status. In the future, we will probably want to revamp the sidebar and these best practices guides. Such bigger change is out of scope of this pull request though!

Checklist

• npm test passes on your machine
• New tests added or existing tests modified to cover all changes
• Code conforms with the style guide
• API Documentation in code was updated
• Documentation in /docs/site was updated
• Affected artifact templates in packages/cli were updated
• Affected example projects in examples/* were updated

[shimks]

Is this PR related to #1094? If it is, would you like to do the rest of its criteria in this PR as well?

[bajtos]

Is this PR related to #1094? If it is, would you like to do the rest of its criteria in this PR as well?

No, not related.

[shimks]

In that case, can we just make sure to check off > Move 'Testing your Application' under this section in #1094 once this PR lands? It's not a big deal though.

[shimks]

On second thought, I believe this is the first time we introduce two links that map to the same address (Testing-your-extension). Should we go forward with this?

[bajtos]

On second thought, I believe this is the first time we introduce two links that map to the same address (Testing-your-extension). Should we go forward with this?

Why not? As I see it, the left sidebar acts as a signpost, allowing users to quickly find their way around our docs. I would like to see "Testing-your-extension" when looking for best practices (that's why it's under "Best practices"). Users learning about extensions and how to write them would like to find this document too, that's why it's under "Extending LoopBack 4" too.