Exercise: DeepWiki – as a tester
Bring a link to a public github repo – preferably, a repo you know.
If you can't, then use
- curl https://github.com/curl/curl (glorious, huge, explored by me here) or
- a tiny thing of mine https://github.com/workroomprds/puzzle_0XX-_candidate01
(my one is the core logic for a simple blackbox puzzle. You can run the tests at https://exercises.workroomprds.com/deepwiki_for_testers/testRunner.html )
Paste it into DeepWiki (or just change the github to deepwiki in the URL):
DeepWiki | AI documentation you can talk to, for every repo
DeepWiki provides up-to-date documentation you can talk to, for every repo in the world. Think Deep Research for GitHub - powered by Devin.
Exercise
Primer
5 mins
Primer: If you're coming into a new repo, where might you start? System diagrams? Tests? Entry points? Tech stack? User needs? Value? Risks? Open bugs? PRs? Decision records? Add your own...
Deepwiki is based on the code and the config: it won't be appropriate for things not described in code. From the list, what might those be?
Explore
10 mins
Dig in!
My guidance (should you need it)
- Find and read some sort of Quick Start Guide, pick holes in it, spot things you didn't already know, check them. My tiny repo is too pointless to have one...
- Take a look at the table of contents (the list on the left) – what parts interest you as a tester?
- Go look at a part you know well. Find accuracies, misconceptions, absences and over-complications.
- Enumerate: Find several different ways that code is (or data are) represented.
- Ask the thing a question – maybe about the tests, or the architecture.
- Gauge whether the information is an up-to-date representation of the repo (hint: it's not).
Share
5 mins
Share your thoughts
Comments
Sign in or become a Workroom Productions member to read and leave comments.