Add Testing pages

[sarjona]

I've started migrating Testing pages, like https://docs.moodle.org/dev/Testing and https://docs.moodle.org/dev/Testing_of_integrated_issues.

While working on this patch, I've also updated the content of these pages:

• I've removed references to Wednesday (as testing day)
  in the Testing integrated issues, because we're not
  following this approach anymore.
• I've added a reference and link to Behat on the Testing page.

QUESTION 1: Can a page have no sidebar assigned? I can put the
"Testing integrated issues" into the "Testing" section, but
that's something we might face on other pages. How should we
deal with them?

QUESTION 2: Apart from that, how many category levels we'll support/have?

[andrewnicols]

QUESTION 1: Can a page have no sidebar assigned? I can put the
"Testing integrated issues" into the "Testing" section, but
that's something we might face on other pages. How should we
deal with them?

For auto-generated sidebars, no. You can't do it but it is apparently on the roadmap.
For manually generated sidebars, yes. You can either not put it in the sidebar configuration, or create a {type: 'ref'} (link).

QUESTION 2: Apart from that, how many category levels we'll support/have?

I would imagine that we don't want it too deep. I'd suggest that three levels is probably the most we want most of the time. That's what I'm looking at for the Acitivty module plugin type.

[sarjona]

Andrew, thanks for answering the questions I raised and helping me to find a way to deal with sidebar for pages that are not displayed in sidebar! :-)
As you'll see, I've added a separate commit for it (in order to make it easier to document this change).

For now, this patch migrates the following pages:

• https://docs.moodle.org/dev/Testing
• https://docs.moodle.org/dev/Testing_of_integrated_issues
• https://docs.moodle.org/dev/QA_testing

I have under my radar other testing pages but, for now, I think it's better to get those and then create a separate patch for the rest :-)

[andrewnicols]

Thanks for working on this Sara,

The changes look awesome :) I've added a few notes, mostly relating to grammar, but a few relating to the use of admonitions and other items.

I feel like we should try to write in full sentences - especially in the admonitions when linking to docs. We should also avoid using them as a stylish wait of adding a header. They should really have content.

Finally I think we should think about our terminology and try to be consistent with it - specifically that we shoudl call the iTeam the "Integration team" in all docs rather than use the colloquialism.

Looks great :) 💃

[sarjona]

Thanks for the review, Andrew! :-) It looks better now!! <3

As you'll see, I've moved testing-integrated-issues and qatesting to the testing folder (inside process), and also renamed these files (to remove the redundant testing).

Apart from the changes, I've also created the Testing category... In fact, I was wondering if we should split "Process & policies" in two separate items in the navbar (in a different issue): it will remove one level in the sidebar and will help users to find information (because there will different pages for Process and Policies) ;-) What do you think?

[andrewnicols]

Thanks Sara,

Let's move the discussion of the organisation to a different issue but my concern about that is that things become a little too separate. We can try it though and see how it looks!

[sarjona]

I've created a PoC (and a pull-request) with the proposal for the navbar I mentioned here, to split Process and Policies: #46