Add testing of deployed Moodle site to the CI process about moodle

[SorraTheOrc]

For clarity step 3, the load testing step, should only occur on demand or during preparation of a release. This is an expensive and time consuming set of tests.

[hosungsmsft]

Rephrased this issue title for v1.5.1, where we focus on no. 2 of this issue (1 is done now). 3 (load testing running) is not scoped in here.

[hosungsmsft]

FYI, all the necessary information for testing the deployed site is available from az group deployment show -g $AZURE_RESOURCE_GROUP -n azuredeploy --query properties.outputs. You can add the next-level field name in the --query properties.outputs to get a specific output, or simply use jq to extract needed information from the JSON output.

[roperto]

Hi @hosungsmsft -- I've noticed you added "CI only master branch". Is there a reason behind that?

I think it would be nice to have it for all branches. It is common, for example, to create a feature branch and do all dev work on that before merging back into master, and it would be nice to have the CI running on those branches too.

See: dcceea9#diff-354f30a63fb0907d4ad57269548329e3R4

What do you think?

Cheers

[hosungsmsft]

@roperto -- Thanks for your question. My reasoning behind that restriction was that the full CI that includes the test deployment might be unnecessarily costly for non-master branches (time-wise and Azure cost-wise). I'd be totally fine if the linting part of the CI is run on every branch, and I suppose that can be programmatically controlled using some env var? What do you think? Thanks!

[roperto]

@hosungsmsft -- That is a good point, I created #90 to separate it from this thread and I will continue working on this issue. Thank you for the feedback.

[hosungsmsft]

Fixed in #91