Testing a Puzzle-Based Game

[verysunshine]

After my last game had several bugs and non-technical issues because it wasn't tested thoroughly before release, I want to test the next one. The trouble is that the main mechanic is like a puzzle hunt puzzle - the correct answer is always an English word or phrase. I feel like if I release a beta build, I would have to either change the puzzles before the final release or have the most enthusiastic players finish the game before it's done.

Thoughts?

[Mutive]

The more testing the better. Even the *best* games have bugs, and certain bugs can both kill the game and any enjoyment the player hopes to derive from it. (This is true even for 'non-technical' bugs. If puzzles are too hard to solve, especially for reasons like objects not being clickable, not going into inventory when placed there the first time, etc., players won't want to solve them.)

You can definitely do the beta build thing and change the puzzles (or not). Another option is to find play testers (here or elsewhere) who are willing to offer advice prior to release. You can swear them to secrecy via an NDA or not. (I'm honestly not all that worried that anyone's going to 'spoil' the game. Like, who are they going to tell who'd actually care? But YMMV and I don't think an NDA is unreasonable.)

I had a lot of luck asking my Facebook friends to playtest, with the additional advantage that some are professional game devs, which meant they were able to both offer a player perspective as well as a "you could add these features that would be especially awesome" one. But even players who literally just fiddle with the game for an hour can tell you whether something's crashing the game/ making it not fun / where they're getting stuck / how long a puzzle is taking /whether the controls are confusing / etc.