Improve testing subsection in profiling intro episode

[JostMigenda]

In our experience running the course at KCL, a significant fraction of learners is mainly using Python in Jupyter notebooks. In that scenario, the existing pytest subsection isn’t really applicable.

I think it might be helpful to start out with something like “as a first step, use a small sample data set and make sure that, after your changes, you still get the same result as before”. (I.e., effectively suggest an integration test.) And then add unit testing with pytest as a next step, for more thorough testing.

[Robadob]

This sounds sensible. As I think I said, the notebook profiling bit was added late after a student only knew how to Python inside of notebooks. The testing bit possibly got overlooked, as that student may have turned up late and missed the start.

Keen to keep it simple though, as testing is enough content to be it's own half day course (e.g. https://fair2-for-research-software.github.io/python-testing-for-research / https://carpentries-incubator.github.io/python-testing/ which can be linked in a call out [Both these courses are "python testing and CI" but their content looks quite different, the latter untouched in 5 years so CI part possibly outdated]).

off-topic: I'd love if carpentries workbench supported tabbed boxes to have side by side python inside/outside notebook (e.g. like python/c++ here), but I don't think it's supported and I'm not familiar enough with their back-end to trivially add it. Maybe a variant of the spoiler block with multiple sections would be easier to add.

[Robadob]

off-topic: I'd love if carpentries workbench supported tabbed boxes to have side by side python inside/outside notebook

It does exist 🤦‍♂️

https://carpentries.github.io/sandpaper-docs/component-guide.html#tabbed-callouts

The first tab specified is the default tab. Selecting a tab in one tab group changes the tab in
the other group(s).

::::::::::::::::::::: group-tab

### Windows

1

### Mac

2

### Linux

3

:::::::::::::::::::::::::::::::

[JostMigenda]

From a recent discussion on the RSESoc Slack: We could point to this Carpentries Incubator course or this CodeRefinery course for further reading.

[Robadob]

From a recent discussion on the RSESoc Slack: We could point to this Carpentries Incubator course or this CodeRefinery course for further reading.

Given the usage is often that people fork these courses to make minor local changes. Might be worth us making a note (in an instructor setup page that doesn't currently exist? or the readme?) of where things like that are, so instructors can more easily switch suitable links to their local equivalent courses where it makes sense.

I don't think it's currently possible to directly use bespoke things from config.yml in the pages.

E.g. this shef version would probably want to point to the fair4rse version, which runs locally, but the incubator version can definitely point to whichever is "best".

This kind of makes the case that incubator should be the root, rather than shef version.