diff --git a/01-introduction.html b/01-introduction.html
index 30357492..9bab96e1 100644
--- a/01-introduction.html
+++ b/01-introduction.html
@@ -420,7 +420,7 @@ <h3 class="callout-title">Keypoints<a class="anchor" aria-label="anchor" href="#
   "identifier": "https://softwaresaved.github.io/fair-research-software/01-introduction.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-10-04",
-  "datePublished": "2023-12-05"
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/02-tools.html b/02-tools.html
index 3e01e7ca..bb627d6d 100644
--- a/02-tools.html
+++ b/02-tools.html
@@ -417,7 +417,7 @@ <h3 class="callout-title">Keypoints<a class="anchor" aria-label="anchor" href="#
   "identifier": "https://softwaresaved.github.io/fair-research-software/02-tools.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-10-04",
-  "datePublished": "2023-12-05"
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/03-version-control.html b/03-version-control.html
index c8f49199..7cc8d338 100644
--- a/03-version-control.html
+++ b/03-version-control.html
@@ -433,7 +433,7 @@ <h3 class="callout-title">Keypoints<a class="anchor" aria-label="anchor" href="#
   "identifier": "https://softwaresaved.github.io/fair-research-software/03-version-control.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-11-13",
-  "datePublished": "2023-12-05"
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/04-code-readability.html b/04-code-readability.html
index 01d5f5f0..7b944781 100644
--- a/04-code-readability.html
+++ b/04-code-readability.html
@@ -434,7 +434,7 @@ <h3 class="callout-title">Keypoints<a class="anchor" aria-label="anchor" href="#
   "identifier": "https://softwaresaved.github.io/fair-research-software/04-code-readability.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-11-13",
-  "datePublished": "2023-12-05"
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/05-code-testing.html b/05-code-testing.html
index 0d42bdd4..4600040e 100644
--- a/05-code-testing.html
+++ b/05-code-testing.html
@@ -295,7 +295,7 @@ <h2 class="accordion-header" id="flush-headingTwelve">
       </div>
       <hr></nav><main id="main-content" class="main-content"><div class="container lesson-content">
         <h1>Code testing</h1>
-        <p> Last updated on 2023-10-18 | 
+        <p> Last updated on 2023-12-11 | 
         
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/05-code-testing.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
         
@@ -314,7 +314,14 @@ <h2 class="card-header">Overview</h2>
 <div class="card-body">
 <div class="inner">
 <h3 class="card-title">Questions</h3>
-<ul><li>…</li>
+<ul><li>Why do we test scientific code?</li>
+<li>What is a unit-test?</li>
+<li>What makes a good unit-test?</li>
+<li>What are the benefits of writing unit-tests?</li>
+<li>What are the benefits of automating unit-tests?</li>
+<li>How can we ensure that our code is well-tested?</li>
+<li>When should we start writing tests?</li>
+<li>Which parts of our code should we prioritise for testing?</li>
 </ul></div>
 </div>
 </div>
@@ -322,7 +329,20 @@ <h3 class="card-title">Questions</h3>
 <div class="card-body">
 <div class="inner bordered">
 <h3 class="card-title">Objectives</h3>
-<ul><li>…</li>
+<ul><li>Setup unit-testing framework pytest</li>
+<li>Create a simple unit-test to check that a function outputs the
+expected value for a given set of valid inputs</li>
+<li>Create a simple unit-test to check that a function raises an error
+when provided with invalid inputs</li>
+<li>Create a full test suite for a simple piece of code using a range of
+different assert statements</li>
+<li>Run a pytest test suite and interpret the results</li>
+<li>Generate a code coverage report with pytest-cov and use it to
+identify parts of a simple piece of code that require additional
+tests</li>
+<li>Convert a bug into a failing test</li>
+<li>Assess whether a piece of third-party code is suitable for reuse
+based on whether it includes sufficient tests</li>
 </ul></div>
 </div>
 </div>
@@ -349,7 +369,31 @@ <h3 class="card-title">Objectives</h3>
 <h3 class="callout-title">Keypoints<a class="anchor" aria-label="anchor" href="#keypoints1"></a>
 </h3>
 <div class="callout-content">
-<ul><li>…</li>
+<ul><li>Formal testing of scientific code is important to demonstrate to
+ourselves and to our readers that our code does what is supposed to
+do.<br></li>
+<li>An absence of tests makes our software risky for others to use and
+as a result, may reduce its impact.</li>
+<li>Unit tests are software tests intended to demonstrate that each
+component of our code e.g. individual functions work as expected. Unit
+tests typically contain assertions that specify how we expect our code
+to behave under a given set of conditions.<br></li>
+<li>A good unit test should focus on verifying a single aspect of a
+function’s behaviour.<br></li>
+<li>Unit testing has many benefits including: (i) it reduces the
+probability that our code contains errors and (ii) it encourages us to
+write readable, modular code.</li>
+<li>Unit tests can be automated using a unit-testing framework such
+e.g. Pytest for Python. Test automation allows us to add new
+functionality or refactor parts of our code and easily check whether it
+still works as expected after our changes.</li>
+<li>Code coverage is a metric that tells us the percentage of lines of
+code in our software that are run when our tests are executed. A code
+coverage report can help us to identify parts of our code that may need
+additional tests.</li>
+<li>If we need to prioritise where we focus our testing efforts we
+should focus on the parts of our code that are “highest risk” i.e. could
+affect the correctness of our research findings.</li>
 </ul></div>
 </div>
 </div>
@@ -416,8 +460,8 @@ <h3 class="callout-title">Keypoints<a class="anchor" aria-label="anchor" href="#
   "url": "https://softwaresaved.github.io/fair-research-software/05-code-testing.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/05-code-testing.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2023-10-18",
-  "datePublished": "2023-12-05"
+  "dateModified": "2023-12-11",
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/06-documenting-code.html b/06-documenting-code.html
index cafb1e1b..7d15835e 100644
--- a/06-documenting-code.html
+++ b/06-documenting-code.html
@@ -417,7 +417,7 @@ <h3 class="callout-title">Keypoints<a class="anchor" aria-label="anchor" href="#
   "identifier": "https://softwaresaved.github.io/fair-research-software/06-documenting-code.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-10-18",
-  "datePublished": "2023-12-05"
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/07-research-ethics.html b/07-research-ethics.html
index 4fd770d2..47d5e4f4 100644
--- a/07-research-ethics.html
+++ b/07-research-ethics.html
@@ -417,7 +417,7 @@ <h3 class="callout-title">Keypoints<a class="anchor" aria-label="anchor" href="#
   "identifier": "https://softwaresaved.github.io/fair-research-software/07-research-ethics.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-10-18",
-  "datePublished": "2023-12-05"
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/08-open-collaboration.html b/08-open-collaboration.html
index b5295580..7109f264 100644
--- a/08-open-collaboration.html
+++ b/08-open-collaboration.html
@@ -417,7 +417,7 @@ <h3 class="callout-title">Keypoints<a class="anchor" aria-label="anchor" href="#
   "identifier": "https://softwaresaved.github.io/fair-research-software/08-open-collaboration.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-10-18",
-  "datePublished": "2023-12-05"
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/09-wrap-up.html b/09-wrap-up.html
index 9831a072..45aa7374 100644
--- a/09-wrap-up.html
+++ b/09-wrap-up.html
@@ -400,7 +400,7 @@ <h3 class="callout-title">Keypoints<a class="anchor" aria-label="anchor" href="#
   "identifier": "https://softwaresaved.github.io/fair-research-software/09-wrap-up.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-10-03",
-  "datePublished": "2023-12-05"
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/404.html b/404.html
index 9fb72793..d722bfaa 100644
--- a/404.html
+++ b/404.html
@@ -352,8 +352,8 @@ <h1>Page not found</h1>
   "url": "https://softwaresaved.github.io/fair-research-software/404.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/404.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2023-12-05",
-  "datePublished": "2023-12-05"
+  "dateModified": "2023-12-11",
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/AUTHORS.html b/AUTHORS.html
index c787283f..2aa190da 100644
--- a/AUTHORS.html
+++ b/AUTHORS.html
@@ -364,7 +364,7 @@ <h1></h1>
   "identifier": "https://softwaresaved.github.io/fair-research-software/AUTHORS.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-11-13",
-  "datePublished": "2023-12-05"
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/CODE_OF_CONDUCT.html b/CODE_OF_CONDUCT.html
index 100c4abf..fb47f5e9 100644
--- a/CODE_OF_CONDUCT.html
+++ b/CODE_OF_CONDUCT.html
@@ -368,7 +368,7 @@ <h1>Contributor Code of Conduct</h1>
   "identifier": "https://softwaresaved.github.io/fair-research-software/CODE_OF_CONDUCT.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-10-03",
-  "datePublished": "2023-12-05"
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/LICENSE.html b/LICENSE.html
index fc819aee..b87db18b 100644
--- a/LICENSE.html
+++ b/LICENSE.html
@@ -419,7 +419,7 @@ <h1>Licenses</h1>
   "identifier": "https://softwaresaved.github.io/fair-research-software/LICENSE.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-10-03",
-  "datePublished": "2023-12-05"
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/aio.html b/aio.html
index e720a448..8c431346 100644
--- a/aio.html
+++ b/aio.html
@@ -654,7 +654,7 @@ <h3 class="callout-title">Keypoints<a class="anchor" aria-label="anchor" href="#
  -->
 </section></section><section id="aio-05-code-testing"><p>Content from <a href="05-code-testing.html">Code testing</a></p>
 <hr>
-<p> Last updated on 2023-10-18 | 
+<p> Last updated on 2023-12-11 | 
         
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/05-code-testing.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 <div class="text-end">
@@ -668,7 +668,14 @@ <h2 class="card-header">Overview</h2>
 <div class="inner">
 <h3 class="card-title">Questions</h3>
 <ul>
-<li>…</li>
+<li>Why do we test scientific code?</li>
+<li>What is a unit-test?</li>
+<li>What makes a good unit-test?</li>
+<li>What are the benefits of writing unit-tests?</li>
+<li>What are the benefits of automating unit-tests?</li>
+<li>How can we ensure that our code is well-tested?</li>
+<li>When should we start writing tests?</li>
+<li>Which parts of our code should we prioritise for testing?</li>
 </ul>
 </div>
 </div>
@@ -678,7 +685,20 @@ <h3 class="card-title">Questions</h3>
 <div class="inner bordered">
 <h3 class="card-title">Objectives</h3>
 <ul>
-<li>…</li>
+<li>Setup unit-testing framework pytest</li>
+<li>Create a simple unit-test to check that a function outputs the
+expected value for a given set of valid inputs</li>
+<li>Create a simple unit-test to check that a function raises an error
+when provided with invalid inputs</li>
+<li>Create a full test suite for a simple piece of code using a range of
+different assert statements</li>
+<li>Run a pytest test suite and interpret the results</li>
+<li>Generate a code coverage report with pytest-cov and use it to
+identify parts of a simple piece of code that require additional
+tests</li>
+<li>Convert a bug into a failing test</li>
+<li>Assess whether a piece of third-party code is suitable for reuse
+based on whether it includes sufficient tests</li>
 </ul>
 </div>
 </div>
@@ -712,7 +732,34 @@ <h3 class="callout-title">Keypoints<a class="anchor" aria-label="anchor" href="#
 </h3>
 <div class="callout-content">
 <ul>
-<li>…</li>
+<li>Formal testing of scientific code is important to demonstrate to
+ourselves and to our readers that our code does what is supposed to
+do.<br>
+</li>
+<li>An absence of tests makes our software risky for others to use and
+as a result, may reduce its impact.</li>
+<li>Unit tests are software tests intended to demonstrate that each
+component of our code e.g. individual functions work as expected. Unit
+tests typically contain assertions that specify how we expect our code
+to behave under a given set of conditions.<br>
+</li>
+<li>A good unit test should focus on verifying a single aspect of a
+function’s behaviour.<br>
+</li>
+<li>Unit testing has many benefits including: (i) it reduces the
+probability that our code contains errors and (ii) it encourages us to
+write readable, modular code.</li>
+<li>Unit tests can be automated using a unit-testing framework such
+e.g. Pytest for Python. Test automation allows us to add new
+functionality or refactor parts of our code and easily check whether it
+still works as expected after our changes.</li>
+<li>Code coverage is a metric that tells us the percentage of lines of
+code in our software that are run when our tests are executed. A code
+coverage report can help us to identify parts of our code that may need
+additional tests.</li>
+<li>If we need to prioritise where we focus our testing efforts we
+should focus on the parts of our code that are “highest risk” i.e. could
+affect the correctness of our research findings.</li>
 </ul>
 </div>
 </div>
@@ -1024,8 +1071,8 @@ <h3 class="callout-title">Keypoints<a class="anchor" aria-label="anchor" href="#
   "url": "https://softwaresaved.github.io/fair-research-software/aio.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/aio.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2023-12-05",
-  "datePublished": "2023-12-05"
+  "dateModified": "2023-12-11",
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/images.html b/images.html
index d12fbc0e..4f0c2615 100644
--- a/images.html
+++ b/images.html
@@ -398,8 +398,8 @@ <h2 class="accordion-header" id="flush-headingTwelve">
   "url": "https://softwaresaved.github.io/fair-research-software/images.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/images.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2023-12-05",
-  "datePublished": "2023-12-05"
+  "dateModified": "2023-12-11",
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/index.html b/index.html
index 631ffa21..a52882ed 100644
--- a/index.html
+++ b/index.html
@@ -472,8 +472,8 @@ <h4 class="accordion-header" id="headingSolution3">
   "url": "https://softwaresaved.github.io/fair-research-software/index.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/index.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2023-12-05",
-  "datePublished": "2023-12-05"
+  "dateModified": "2023-12-11",
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/instructor-notes.html b/instructor-notes.html
index 81cdaf6b..02ccc7bc 100644
--- a/instructor-notes.html
+++ b/instructor-notes.html
@@ -397,8 +397,8 @@ <h1>Instructor Notes</h1>
   "url": "https://softwaresaved.github.io/fair-research-software/instructor-notes.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor-notes.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2023-12-05",
-  "datePublished": "2023-12-05"
+  "dateModified": "2023-12-11",
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/instructor/01-introduction.html b/instructor/01-introduction.html
index 640e4b0f..69f568ad 100644
--- a/instructor/01-introduction.html
+++ b/instructor/01-introduction.html
@@ -422,7 +422,7 @@ <h3 class="callout-title">Keypoints<a class="anchor" aria-label="anchor" href="#
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/01-introduction.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-10-04",
-  "datePublished": "2023-12-05"
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/instructor/02-tools.html b/instructor/02-tools.html
index 532e65d3..9f65e7a7 100644
--- a/instructor/02-tools.html
+++ b/instructor/02-tools.html
@@ -419,7 +419,7 @@ <h3 class="callout-title">Keypoints<a class="anchor" aria-label="anchor" href="#
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/02-tools.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-10-04",
-  "datePublished": "2023-12-05"
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/instructor/03-version-control.html b/instructor/03-version-control.html
index 63dc312d..dfccae4d 100644
--- a/instructor/03-version-control.html
+++ b/instructor/03-version-control.html
@@ -435,7 +435,7 @@ <h3 class="callout-title">Keypoints<a class="anchor" aria-label="anchor" href="#
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/03-version-control.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-11-13",
-  "datePublished": "2023-12-05"
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/instructor/04-code-readability.html b/instructor/04-code-readability.html
index bee9a39c..8a73fbcb 100644
--- a/instructor/04-code-readability.html
+++ b/instructor/04-code-readability.html
@@ -436,7 +436,7 @@ <h3 class="callout-title">Keypoints<a class="anchor" aria-label="anchor" href="#
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/04-code-readability.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-11-13",
-  "datePublished": "2023-12-05"
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/instructor/05-code-testing.html b/instructor/05-code-testing.html
index 7f0f82d8..abb6e2d9 100644
--- a/instructor/05-code-testing.html
+++ b/instructor/05-code-testing.html
@@ -295,7 +295,7 @@ <h2 class="accordion-header" id="flush-headingTwelve">
       </div>
       <hr></nav><main id="main-content" class="main-content"><div class="container lesson-content">
         <h1>Code testing</h1>
-        <p> Last updated on 2023-10-18 | 
+        <p> Last updated on 2023-12-11 | 
         
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/05-code-testing.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
         
@@ -316,7 +316,14 @@ <h2 class="card-header">Overview</h2>
 <div class="card-body">
 <div class="inner">
 <h3 class="card-title">Questions</h3>
-<ul><li>…</li>
+<ul><li>Why do we test scientific code?</li>
+<li>What is a unit-test?</li>
+<li>What makes a good unit-test?</li>
+<li>What are the benefits of writing unit-tests?</li>
+<li>What are the benefits of automating unit-tests?</li>
+<li>How can we ensure that our code is well-tested?</li>
+<li>When should we start writing tests?</li>
+<li>Which parts of our code should we prioritise for testing?</li>
 </ul></div>
 </div>
 </div>
@@ -324,7 +331,20 @@ <h3 class="card-title">Questions</h3>
 <div class="card-body">
 <div class="inner bordered">
 <h3 class="card-title">Objectives</h3>
-<ul><li>…</li>
+<ul><li>Setup unit-testing framework pytest</li>
+<li>Create a simple unit-test to check that a function outputs the
+expected value for a given set of valid inputs</li>
+<li>Create a simple unit-test to check that a function raises an error
+when provided with invalid inputs</li>
+<li>Create a full test suite for a simple piece of code using a range of
+different assert statements</li>
+<li>Run a pytest test suite and interpret the results</li>
+<li>Generate a code coverage report with pytest-cov and use it to
+identify parts of a simple piece of code that require additional
+tests</li>
+<li>Convert a bug into a failing test</li>
+<li>Assess whether a piece of third-party code is suitable for reuse
+based on whether it includes sufficient tests</li>
 </ul></div>
 </div>
 </div>
@@ -351,7 +371,31 @@ <h3 class="card-title">Objectives</h3>
 <h3 class="callout-title">Keypoints<a class="anchor" aria-label="anchor" href="#keypoints1"></a>
 </h3>
 <div class="callout-content">
-<ul><li>…</li>
+<ul><li>Formal testing of scientific code is important to demonstrate to
+ourselves and to our readers that our code does what is supposed to
+do.<br></li>
+<li>An absence of tests makes our software risky for others to use and
+as a result, may reduce its impact.</li>
+<li>Unit tests are software tests intended to demonstrate that each
+component of our code e.g. individual functions work as expected. Unit
+tests typically contain assertions that specify how we expect our code
+to behave under a given set of conditions.<br></li>
+<li>A good unit test should focus on verifying a single aspect of a
+function’s behaviour.<br></li>
+<li>Unit testing has many benefits including: (i) it reduces the
+probability that our code contains errors and (ii) it encourages us to
+write readable, modular code.</li>
+<li>Unit tests can be automated using a unit-testing framework such
+e.g. Pytest for Python. Test automation allows us to add new
+functionality or refactor parts of our code and easily check whether it
+still works as expected after our changes.</li>
+<li>Code coverage is a metric that tells us the percentage of lines of
+code in our software that are run when our tests are executed. A code
+coverage report can help us to identify parts of our code that may need
+additional tests.</li>
+<li>If we need to prioritise where we focus our testing efforts we
+should focus on the parts of our code that are “highest risk” i.e. could
+affect the correctness of our research findings.</li>
 </ul></div>
 </div>
 </div>
@@ -418,8 +462,8 @@ <h3 class="callout-title">Keypoints<a class="anchor" aria-label="anchor" href="#
   "url": "https://softwaresaved.github.io/fair-research-software/instructor/05-code-testing.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/05-code-testing.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2023-10-18",
-  "datePublished": "2023-12-05"
+  "dateModified": "2023-12-11",
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/instructor/06-documenting-code.html b/instructor/06-documenting-code.html
index 96ed5c14..a6f7991e 100644
--- a/instructor/06-documenting-code.html
+++ b/instructor/06-documenting-code.html
@@ -419,7 +419,7 @@ <h3 class="callout-title">Keypoints<a class="anchor" aria-label="anchor" href="#
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/06-documenting-code.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-10-18",
-  "datePublished": "2023-12-05"
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/instructor/07-research-ethics.html b/instructor/07-research-ethics.html
index 74faf640..b233782a 100644
--- a/instructor/07-research-ethics.html
+++ b/instructor/07-research-ethics.html
@@ -419,7 +419,7 @@ <h3 class="callout-title">Keypoints<a class="anchor" aria-label="anchor" href="#
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/07-research-ethics.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-10-18",
-  "datePublished": "2023-12-05"
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/instructor/08-open-collaboration.html b/instructor/08-open-collaboration.html
index 089171e4..4e65e27a 100644
--- a/instructor/08-open-collaboration.html
+++ b/instructor/08-open-collaboration.html
@@ -419,7 +419,7 @@ <h3 class="callout-title">Keypoints<a class="anchor" aria-label="anchor" href="#
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/08-open-collaboration.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-10-18",
-  "datePublished": "2023-12-05"
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/instructor/09-wrap-up.html b/instructor/09-wrap-up.html
index 22d937c5..b4c0f0d0 100644
--- a/instructor/09-wrap-up.html
+++ b/instructor/09-wrap-up.html
@@ -402,7 +402,7 @@ <h3 class="callout-title">Keypoints<a class="anchor" aria-label="anchor" href="#
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/09-wrap-up.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-10-03",
-  "datePublished": "2023-12-05"
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/instructor/404.html b/instructor/404.html
index 4b57886c..bd74d577 100644
--- a/instructor/404.html
+++ b/instructor/404.html
@@ -352,8 +352,8 @@ <h1>Page not found</h1>
   "url": "https://softwaresaved.github.io/fair-research-software/instructor/404.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/404.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2023-12-05",
-  "datePublished": "2023-12-05"
+  "dateModified": "2023-12-11",
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/instructor/AUTHORS.html b/instructor/AUTHORS.html
index 41fd11d3..8ba8c59d 100644
--- a/instructor/AUTHORS.html
+++ b/instructor/AUTHORS.html
@@ -366,7 +366,7 @@ <h1></h1>
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/AUTHORS.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-11-13",
-  "datePublished": "2023-12-05"
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/instructor/CODE_OF_CONDUCT.html b/instructor/CODE_OF_CONDUCT.html
index d1cf139a..095f1f32 100644
--- a/instructor/CODE_OF_CONDUCT.html
+++ b/instructor/CODE_OF_CONDUCT.html
@@ -370,7 +370,7 @@ <h1>Contributor Code of Conduct</h1>
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/CODE_OF_CONDUCT.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-10-03",
-  "datePublished": "2023-12-05"
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/instructor/LICENSE.html b/instructor/LICENSE.html
index 2a46d653..7af4bbc5 100644
--- a/instructor/LICENSE.html
+++ b/instructor/LICENSE.html
@@ -421,7 +421,7 @@ <h1>Licenses</h1>
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/LICENSE.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-10-03",
-  "datePublished": "2023-12-05"
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/instructor/aio.html b/instructor/aio.html
index 8af2e968..bb09f823 100644
--- a/instructor/aio.html
+++ b/instructor/aio.html
@@ -660,7 +660,7 @@ <h3 class="callout-title">Keypoints<a class="anchor" aria-label="anchor" href="#
  -->
 </section></section><section id="aio-05-code-testing"><p>Content from <a href="05-code-testing.html">Code testing</a></p>
 <hr>
-<p> Last updated on 2023-10-18 | 
+<p> Last updated on 2023-12-11 | 
         
         <a href="https://github.com/softwaresaved/fair-research-software/edit/main/episodes/05-code-testing.md" class="external-link">Edit this page <i aria-hidden="true" data-feather="edit"></i></a></p>
 <p>Estimated time <i aria-hidden="true" data-feather="clock"></i> 90 minutes </p>
@@ -675,7 +675,14 @@ <h2 class="card-header">Overview</h2>
 <div class="inner">
 <h3 class="card-title">Questions</h3>
 <ul>
-<li>…</li>
+<li>Why do we test scientific code?</li>
+<li>What is a unit-test?</li>
+<li>What makes a good unit-test?</li>
+<li>What are the benefits of writing unit-tests?</li>
+<li>What are the benefits of automating unit-tests?</li>
+<li>How can we ensure that our code is well-tested?</li>
+<li>When should we start writing tests?</li>
+<li>Which parts of our code should we prioritise for testing?</li>
 </ul>
 </div>
 </div>
@@ -685,7 +692,20 @@ <h3 class="card-title">Questions</h3>
 <div class="inner bordered">
 <h3 class="card-title">Objectives</h3>
 <ul>
-<li>…</li>
+<li>Setup unit-testing framework pytest</li>
+<li>Create a simple unit-test to check that a function outputs the
+expected value for a given set of valid inputs</li>
+<li>Create a simple unit-test to check that a function raises an error
+when provided with invalid inputs</li>
+<li>Create a full test suite for a simple piece of code using a range of
+different assert statements</li>
+<li>Run a pytest test suite and interpret the results</li>
+<li>Generate a code coverage report with pytest-cov and use it to
+identify parts of a simple piece of code that require additional
+tests</li>
+<li>Convert a bug into a failing test</li>
+<li>Assess whether a piece of third-party code is suitable for reuse
+based on whether it includes sufficient tests</li>
 </ul>
 </div>
 </div>
@@ -719,7 +739,34 @@ <h3 class="callout-title">Keypoints<a class="anchor" aria-label="anchor" href="#
 </h3>
 <div class="callout-content">
 <ul>
-<li>…</li>
+<li>Formal testing of scientific code is important to demonstrate to
+ourselves and to our readers that our code does what is supposed to
+do.<br>
+</li>
+<li>An absence of tests makes our software risky for others to use and
+as a result, may reduce its impact.</li>
+<li>Unit tests are software tests intended to demonstrate that each
+component of our code e.g. individual functions work as expected. Unit
+tests typically contain assertions that specify how we expect our code
+to behave under a given set of conditions.<br>
+</li>
+<li>A good unit test should focus on verifying a single aspect of a
+function’s behaviour.<br>
+</li>
+<li>Unit testing has many benefits including: (i) it reduces the
+probability that our code contains errors and (ii) it encourages us to
+write readable, modular code.</li>
+<li>Unit tests can be automated using a unit-testing framework such
+e.g. Pytest for Python. Test automation allows us to add new
+functionality or refactor parts of our code and easily check whether it
+still works as expected after our changes.</li>
+<li>Code coverage is a metric that tells us the percentage of lines of
+code in our software that are run when our tests are executed. A code
+coverage report can help us to identify parts of our code that may need
+additional tests.</li>
+<li>If we need to prioritise where we focus our testing efforts we
+should focus on the parts of our code that are “highest risk” i.e. could
+affect the correctness of our research findings.</li>
 </ul>
 </div>
 </div>
@@ -1035,8 +1082,8 @@ <h3 class="callout-title">Keypoints<a class="anchor" aria-label="anchor" href="#
   "url": "https://softwaresaved.github.io/fair-research-software/instructor/aio.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/aio.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2023-12-05",
-  "datePublished": "2023-12-05"
+  "dateModified": "2023-12-11",
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/instructor/images.html b/instructor/images.html
index 1243c3e4..1d1e525e 100644
--- a/instructor/images.html
+++ b/instructor/images.html
@@ -400,8 +400,8 @@ <h2 class="accordion-header" id="flush-headingTwelve">
   "url": "https://softwaresaved.github.io/fair-research-software/instructor/images.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/images.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2023-12-05",
-  "datePublished": "2023-12-05"
+  "dateModified": "2023-12-11",
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/instructor/index.html b/instructor/index.html
index 2d0cbbb1..a66483c1 100644
--- a/instructor/index.html
+++ b/instructor/index.html
@@ -390,7 +390,12 @@ <h3 class="callout-title">Prerequisites<a class="anchor" aria-label="anchor" hre
  5. <a href="05-code-testing.html">Code testing</a>
 </td>
 <td>
-…
+Why do we test scientific code?<br>What is a unit-test?<br>What makes
+a good unit-test?<br>What are the benefits of writing
+unit-tests?<br>What are the benefits of automating unit-tests?<br>How
+can we ensure that our code is well-tested?<br>When should we start
+writing tests?<br>Which parts of our code should we prioritise for
+testing?
 </td>
 </tr><tr><td>
 <span class="visually-hidden">Duration: </span>07h 00m
@@ -577,8 +582,8 @@ <h4 class="accordion-header" id="headingSolution3">
   "url": "https://softwaresaved.github.io/fair-research-software/instructor/index.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/index.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2023-12-05",
-  "datePublished": "2023-12-05"
+  "dateModified": "2023-12-11",
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/instructor/instructor-notes.html b/instructor/instructor-notes.html
index 6baada9e..80851a08 100644
--- a/instructor/instructor-notes.html
+++ b/instructor/instructor-notes.html
@@ -408,8 +408,8 @@ <h1>Instructor Notes</h1>
   "url": "https://softwaresaved.github.io/fair-research-software/instructor/instructor-notes.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/instructor-notes.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2023-12-05",
-  "datePublished": "2023-12-05"
+  "dateModified": "2023-12-11",
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/instructor/key-points.html b/instructor/key-points.html
index 39f8f4ff..994bae30 100644
--- a/instructor/key-points.html
+++ b/instructor/key-points.html
@@ -379,7 +379,34 @@ <h2 class="accordion-header" id="flush-headingTwelve">
 </ul></section><section id="05-code-testing"><h2 class="section-heading"><a href="05-code-testing.html">Code testing</a></h2>
 <hr class="half-width">
 <ul>
-<li>…</li>
+<li>Formal testing of scientific code is important to demonstrate to
+ourselves and to our readers that our code does what is supposed to
+do.<br>
+</li>
+<li>An absence of tests makes our software risky for others to use and
+as a result, may reduce its impact.</li>
+<li>Unit tests are software tests intended to demonstrate that each
+component of our code e.g. individual functions work as expected. Unit
+tests typically contain assertions that specify how we expect our code
+to behave under a given set of conditions.<br>
+</li>
+<li>A good unit test should focus on verifying a single aspect of a
+function’s behaviour.<br>
+</li>
+<li>Unit testing has many benefits including: (i) it reduces the
+probability that our code contains errors and (ii) it encourages us to
+write readable, modular code.</li>
+<li>Unit tests can be automated using a unit-testing framework such
+e.g. Pytest for Python. Test automation allows us to add new
+functionality or refactor parts of our code and easily check whether it
+still works as expected after our changes.</li>
+<li>Code coverage is a metric that tells us the percentage of lines of
+code in our software that are run when our tests are executed. A code
+coverage report can help us to identify parts of our code that may need
+additional tests.</li>
+<li>If we need to prioritise where we focus our testing efforts we
+should focus on the parts of our code that are “highest risk” i.e. could
+affect the correctness of our research findings.</li>
 </ul></section><section id="06-documenting-code"><h2 class="section-heading"><a href="06-documenting-code.html">Documenting code</a></h2>
 <hr class="half-width">
 <ul>
@@ -445,8 +472,8 @@ <h2 class="accordion-header" id="flush-headingTwelve">
   "url": "https://softwaresaved.github.io/fair-research-software/instructor/key-points.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/key-points.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2023-12-05",
-  "datePublished": "2023-12-05"
+  "dateModified": "2023-12-11",
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/instructor/profiles.html b/instructor/profiles.html
index e983f6d7..cb3220a0 100644
--- a/instructor/profiles.html
+++ b/instructor/profiles.html
@@ -321,8 +321,8 @@ <h1>Learner Profiles</h1>
   "url": "https://softwaresaved.github.io/fair-research-software/instructor/profiles.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/profiles.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2023-12-05",
-  "datePublished": "2023-12-05"
+  "dateModified": "2023-12-11",
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/instructor/reference.html b/instructor/reference.html
index fdd17ce4..2dde87a2 100644
--- a/instructor/reference.html
+++ b/instructor/reference.html
@@ -363,7 +363,7 @@ <h1>Reference</h1>
   "identifier": "https://softwaresaved.github.io/fair-research-software/instructor/reference.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-10-03",
-  "datePublished": "2023-12-05"
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/key-points.html b/key-points.html
index e7fef020..ca1be8f0 100644
--- a/key-points.html
+++ b/key-points.html
@@ -377,7 +377,34 @@ <h2 class="accordion-header" id="flush-headingTwelve">
 </ul></section><section id="05-code-testing"><h2 class="section-heading"><a href="05-code-testing.html">Code testing</a></h2>
 <hr class="half-width">
 <ul>
-<li>…</li>
+<li>Formal testing of scientific code is important to demonstrate to
+ourselves and to our readers that our code does what is supposed to
+do.<br>
+</li>
+<li>An absence of tests makes our software risky for others to use and
+as a result, may reduce its impact.</li>
+<li>Unit tests are software tests intended to demonstrate that each
+component of our code e.g. individual functions work as expected. Unit
+tests typically contain assertions that specify how we expect our code
+to behave under a given set of conditions.<br>
+</li>
+<li>A good unit test should focus on verifying a single aspect of a
+function’s behaviour.<br>
+</li>
+<li>Unit testing has many benefits including: (i) it reduces the
+probability that our code contains errors and (ii) it encourages us to
+write readable, modular code.</li>
+<li>Unit tests can be automated using a unit-testing framework such
+e.g. Pytest for Python. Test automation allows us to add new
+functionality or refactor parts of our code and easily check whether it
+still works as expected after our changes.</li>
+<li>Code coverage is a metric that tells us the percentage of lines of
+code in our software that are run when our tests are executed. A code
+coverage report can help us to identify parts of our code that may need
+additional tests.</li>
+<li>If we need to prioritise where we focus our testing efforts we
+should focus on the parts of our code that are “highest risk” i.e. could
+affect the correctness of our research findings.</li>
 </ul></section><section id="06-documenting-code"><h2 class="section-heading"><a href="06-documenting-code.html">Documenting code</a></h2>
 <hr class="half-width">
 <ul>
@@ -443,8 +470,8 @@ <h2 class="accordion-header" id="flush-headingTwelve">
   "url": "https://softwaresaved.github.io/fair-research-software/key-points.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/key-points.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2023-12-05",
-  "datePublished": "2023-12-05"
+  "dateModified": "2023-12-11",
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/md5sum.txt b/md5sum.txt
index 118a950e..995f44e3 100644
--- a/md5sum.txt
+++ b/md5sum.txt
@@ -9,7 +9,7 @@
 "episodes/02-tools.md" "f802f8a37abc6d2105484d135d340ff0" "site/built/02-tools.md" "2023-10-04"
 "episodes/03-version-control.md" "f6483a73d96267f3b08982580318dbd3" "site/built/03-version-control.md" "2023-11-13"
 "episodes/04-code-readability.md" "5315fdee2f7e06ac00af959c4a30a467" "site/built/04-code-readability.md" "2023-11-13"
-"episodes/05-code-testing.md" "01124ce4fb5d90aba753ae96f9a8a075" "site/built/05-code-testing.md" "2023-10-18"
+"episodes/05-code-testing.md" "e66febaf85fb6d2cabce3aac21ba41de" "site/built/05-code-testing.md" "2023-12-11"
 "episodes/06-documenting-code.md" "9a53413544b78f2dbbb51e028309c58a" "site/built/06-documenting-code.md" "2023-10-18"
 "episodes/07-research-ethics.md" "5c471753eeaaa7432d2f18c56916c70d" "site/built/07-research-ethics.md" "2023-10-18"
 "episodes/08-open-collaboration.md" "6c96741ba6fb1b0a39468c2fce658dbf" "site/built/08-open-collaboration.md" "2023-10-18"
diff --git a/pkgdown.yml b/pkgdown.yml
index 479e88a6..b372e949 100644
--- a/pkgdown.yml
+++ b/pkgdown.yml
@@ -2,5 +2,5 @@ pandoc: 2.19.2
 pkgdown: 2.0.7
 pkgdown_sha: ~
 articles: {}
-last_built: 2023-12-05T00:34Z
+last_built: 2023-12-11T12:51Z
 
diff --git a/profiles.html b/profiles.html
index 1c84d8f7..a44eea60 100644
--- a/profiles.html
+++ b/profiles.html
@@ -321,8 +321,8 @@ <h1>Learner Profiles</h1>
   "url": "https://softwaresaved.github.io/fair-research-software/profiles.html",
   "identifier": "https://softwaresaved.github.io/fair-research-software/profiles.html",
   "dateCreated": "2023-10-03",
-  "dateModified": "2023-12-05",
-  "datePublished": "2023-12-05"
+  "dateModified": "2023-12-11",
+  "datePublished": "2023-12-11"
 }
 
   </script><script>
diff --git a/reference.html b/reference.html
index bce05040..dd6d1cb5 100644
--- a/reference.html
+++ b/reference.html
@@ -361,7 +361,7 @@ <h1>Reference</h1>
   "identifier": "https://softwaresaved.github.io/fair-research-software/reference.html",
   "dateCreated": "2023-10-03",
   "dateModified": "2023-10-03",
-  "datePublished": "2023-12-05"
+  "datePublished": "2023-12-11"
 }
 
   </script><script>