Video evidence is a helpful way to demonstrate the “dynamics of a system” [1]. If your product has animations, gameplay, or other dynamic functionality that cannot be effectively demonstrated with screenshots, video evidence is worth considering.
You should use a sensible folder structure to organise your video evidence. Rather than one long video showing everything, a series of shorter videos (30–40 seconds) with descriptive file names is a much more accessible way of presenting evidence [1]. You should reference these files by name when presenting your testing evidence, including time stamps and a brief description of what the video shows [1].
You could name the files using the test name they relate to or name them after a testing section and use time stamps in your test table [1].
Mechanics of capturing video
If using Windows, you could use the Game Bar.
If using macOS, you could use either the Screenshot app or QuickTime Player.
If you are comfortable installing third-party software to record your screen (or are using Linux), you could use OBS Studio.
720p is likely more than good enough and will keep file sizes small which is helpful when your teachers come to send your work to the exam board; there is no need for 4k [1].
References
-
[1]Cambridge OCR 2026. A Level Computer Science: A Guide to Creating Concise NEA Documentation.