Autumn 2026 review

[mmesiti]

Tries to address all issues in #245.

This PR will contain many independent bits, please use the code review feature to choose which changes should be approved.
I will add comments there too.

View the content rendered: https://mmesiti.github.io/cr-testing/branch/aut2026review/cloud/ (haven't thanked @frankier for finding and showing me the trick to see the rendering of branches other than main, and also @rkdarst for adding that feature to the github workflow).

I can't add @Vinye to the reviewers it seems, but she's definitely got a say here :-)

Updated 10.09 with link to rendered pages

[johanhellsvik]

Good editing and additions to the lesson contents. Highlighting here a few things that I think are good improvements

• The new contents under "In this lesson we discuss the basics of automated testing." read well.
• The extended "Testing vocabulary" is most valuable.
• The change of wording "continuous integration" -> "cloud" as in the change"Exercise CI-1: Create and use a continuous integration workflow on GitHub or GitLab" to "Exercise CI-1: Create and use a workflow on GitHub or a pipeline on GitLab" is good for clarity. I agree that the expression "continuous integration" can have different meanings in different contexts.

My only specific suggestion for change/addition is that one could perhaps somewhere that a workflows/pipelines need not necessarily be on the cloud, but could alternatively be on e.g. a self hosted GitHub or GitLab server.

[Vinye]

This exercise is rendered inside the above note, is that intentional?
I'm looking at this: https://mmesiti.github.io/cr-testing/branch/aut2026review/cloud/

I don't know enough sphinx syntax to resolve this.

[mmesiti]

It would be sufficient to add a "" before the challenge block, to properly close the note block. But I can't do this on github with a suggestion, interestingly, because the additional in the suggestion would close the suggestion block instead of being added to the document, and I don't know how to "escape" the "```" so that this doesn't happen...

[mmesiti]

Should be fixed now (done locally)

[Vinye]

I did a proofreading of the changes, caught some minor things 🔎

[mmesiti]

Thank you @johanhellsvik for the prompt review!

My only specific suggestion for change/addition is that one could perhaps somewhere that a workflows/pipelines need not necessarily be on the cloud, but could alternatively be on e.g. a self hosted GitHub or GitLab server.

This made me think a bit.

I would have argued that a self hosted github or gitlab server would still qualify as cloud (might be a "private" cloud), BUT I realised that I might be using "cloud" in an improper way (in the same way I thought that "continous integration" was used slightly ambiguously before, so we decided to get rid of the term).

Maybe a more elegant approach would be to get rid of "cloud" and just say "remotely", so we would have

# Automated testing on your computer 
...
# Automated testing remotely

What do you think? Poking @Vinye since she was definitely part of the discussion.

[mmesiti]

After fixing the cloud/remote wording issue (waiting on your opinion), there are 2 alternative ways to go forward:

1. In oder to have a clear diff between changes you have already reviewed and further changes: mark this PR as ready for merge, merge it, and make another PR with the other changes mentioned in Autumn 2026 revision #245
2. In order to keep a bigger picture of all the changes between the current main and the next: keep adding to this PR.

What do @Vinye and @johanhellsvik think? Sorry for spamming mentions.

[Vinye]

I would have argued that a self hosted github or gitlab server would still qualify as cloud (might be a "private" cloud), ...

While this is true, for me the word "cloud" first associates with the big providers and it doesn't connect in my head with self-hosting. Remotely is a fine choice, although another word that came to my mind is server, how about it?

Also, now that we are thinking about our word choices to accomodate self-hosting, should we mention self-hosting as an option somewhere? Along the lines of "besides Github Actions and Gitlab pipelines, self-hosting your test servers is also an option, but we won't cover that here"

P.S. I'd prefer merging this (option 1)

[mmesiti]

I'd merge this. There will be chances to do further review for another batch of changes. @Vinye ok?

[Vinye]

OK

[mmesiti]

My only specific suggestion for change/addition is that one could perhaps somewhere that a workflows/pipelines need not necessarily be on the cloud, but could alternatively be on e.g. a self hosted GitHub or GitLab server.

This is being addressed in #252