Add writing your first unit test

[connoraird]

Adds a new episode for writing your first unit test

closes #34

[github-actions]

Thank you!

Thank you for your pull request 😃

🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

• 🎯 correct output
• 🖼️ correct figures
• ❓ new warnings
• ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/UCL-ARC/fortran-unit-testing-lesson/compare/md-outputs..md-outputs-PR-36

The following changes were observed in the rendered markdown documents:

 3-writing-your-first-unit-test.md (new)            | 99 ++++++++++++++++++++++
 ...test-syntax.md => 4-fortran-unit-test-syntax.md |  4 +-
 ...-broken-test.md => 5-debugging-a-broken-test.md |  6 +-
 ...-parallel-code.md => 6-testing-parallel-code.md |  4 +-
 config.yaml                                        |  7 +-
 md5sum.txt                                         |  9 +-
 6 files changed, 115 insertions(+), 14 deletions(-)

What does this mean?

If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible.

This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.

⏱️ Updated at 2025-12-05 16:53:17 +0000