feat(qa): add mcq (#145) and activity

Author: amyheather

pages/guide/verification_validation/quality_assurance.qmd

@@ -232,3 +232,61 @@ Key resources to check out when planning your quality assurance:
 * The [Quality assurance of code for analysis and research](https://best-practice-and-impact.github.io/qa-of-code-guidance/intro.html) book from the Government Analysis Function.
 
 * [Facets of trust in simulation studies](https://doi.org/10.1016/j.ejor.2020.06.043) - a framework for thinking about different dimensions of trust in simulation work and how they evolve over a study’s lifecycle.
+
+## Test yourself
+
+<div class="h3-tight"></div>
+
+### Quiz
+
+```{r}
+#| echo: false
+library(webexercises) # nolint: library_call_linter
+```
+
+::: {.callout-note}
+
+## Which statement best describes quality assurance (QA) in analytical projects?
+
+```{r}
+#| output: asis
+#| echo: false
+cat(longmcq(c(
+  "A one-off final check of results before publication.",
+  "A process limited to testing code for bugs.",
+  answer = paste0(
+    "A formal, systematic process of planning checks, carrying them out, and ",
+    "keeping evidence."
+  )
+)))
+```
+
+:::
+
+::: {.callout-note}
+
+## Which option best captures the relationship between QA, verification, and validation as described on the page?
+
+```{r}
+#| output: asis
+#| echo: false
+cat(longmcq(c(
+  "QA and verification are the same; validation is separate.",
+  answer = "Verification and validation are specific checks within QA.",
+  "Validation replaces QA in higher‑risk projects."
+)))
+```
+
+:::
+
+### Activity
+
+Reflect on how you might apply quality assurance to the simulation model you have been developing, or to another recent piece of analytical work. At a minimum, write down:
+
+* The decision the work is intended to inform.
+* Who could act as commissioner, analyst, assurer, and approver (even if some roles are combined).
+* A few QA activities you could realistically do when (a) scoping, (b) design, (c) analysis, and (d) delivery.
+
+You could also have a go creating a **GitHub Project**, adding some QA items as issues. You could then treat open items as your QA plan and closed items as your QA log.
+
+<br><br>