- First, I test it. If I can't break it, we're doing great.
- Then, I make my husband test it. He's a software developer, and he ususally works okay after I remind him that if his testers don't come back with extremely detailed reports he gets mad, so yes, actually, he is expected to play my game longer than 30 seconds.
- At this point, I stop and fix things that he's found.
- I send it out to my local programming club's discord.
- I beg for testers on Bluesky. Seriously, don't sleep on this step, plenty of people are willing and ready to help you. Use the #indiedev and #gamedev hashtags.
- I take the comments, and if I like the suggestions, I integrate them into the next build. I don't always change everything. That's art, baybay. But I do pretty much 95% of what my testers say, because the program has to make sense to people who aren't me.
- My programming club, my husband, and Bluesky all get copies again to beta test
- HOPEFULLY that's the final boss of testing and I can go on to something else
Wednesday, February 19, 2025
My Testing Process
This is a screenshot from my newest project! I don't have it named though. But the pink axolotl is Delia. It's an educational game. If you're old like me, this game is similar enough to Treasure Mountain, it just has a fresh coat of paint on it. It's through it's first testing phase, and everything has gone great so far! That's a lie, the first test was actually kinda rough -- that's what testers are for. I thought it might help if I outline my current testing process. If it helps, you can steal it.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment