we’ll also steer clear of Shiny/Rmarkdown/Quarto, as things can be a bit more tricky to test there
we also won’t talk about debugging here (although do look out for the future training session on that)
Informal testing
a real-world example: Teams transcripts
Teams transcripts can be very useful data-sources
but they’re absolutely horrible to work with:
WEBVTTQ1::>00:00:00.000 --> 00:00:14.080<v Brendan Clarke> this was the first question in the transcript00:00:14.080 --> 00:00:32.180<v Someone Else> then someone replied with this answerQ2::>00:00:32.180 --> 00:00:48.010<v Brendan Clarke> then there was another question00:00:48.010 --> 00:00:58.010<v Someone Else> and another tedious response
imagine that you’ve written a (horrible) Teams transcript parser:
how would you test this code to make sure it behaves itself?