I work for a test consultantant company that occasionally attends career fairs.
For engagement at our booth we have a little bug-hunt game. A version of the company website with some bugs added, that people can explore, find a bug, write a short bug report and get the chance to win a prize.
But as someone who spends more of their time digging through logs rather than exploring an UI, I would also like to show another side of testing.
So I´m looking for something with a similar concept but more “log focused” and preferably not related to a webpage (for variety).
Maybe something like: run a testcase → get a log → try to find out what went wrong.
It should be simple enough to not scare away anyone who has never done it before but still a bit of a challenge.
Does anyone know of anything like that?
I also don´t think it would be that hard to create something from scratch but why reinvent the wheel unless you have to.
Hey,
Good idea to advertise logs a bit as a means to support testing.
‘run a testcase → get a log → try to find out what went wrong’
This could be expanded as there are more things available. I’ve used the logs before to see things like:
What happened each time when I did a thing in the app?
What event happened in the meantime done by the system or other app users that might have impacted what I did or intend to do?
Find if there’s a potential issue(which is visible in the logs only) - without knowing everything you should look for;
Find if there’s another effect besides what you see wrong directly from your test; has your test triggered another event that caused an issue elsewhere?
Since it´s supposed to be a game, it would be fun to have things of varying “difficulty”. I see ‘run a testcase → get a log → try to find out what went wrong’ as the easiest level to start with. Maybe the program is supposed to run a calculation and accidentally gets the wrong input or uses the wrong operator.
But I would also like to have scenarios where the program does what it should but it´s the testcase that is wrong.