Post by sirtawmis in Walkthrough

Viewing post in Walkthrough

I also think it's better not to have a walk through... there's a thread I made, for asking for hints -

But an overall walk through would make most of us just following it making finding potential bugs much more difficult. It's better that we all try to do it ourselves, and post results if we find something odd.

Like Reply

Burzmali5 years ago

The issue is that the game isn't necessarily in a state that a clean run through would be successful, we need to start there, then worry about the edge and corner cases.

Like Reply

sirtawmis5 years ago (1 edit)

For beta testing; I see it the other way. It's better to not know what needs to be done and click random things and see if it breaks something or creates an unexpected result.

That's my thinking anyway. Certainly not the right and only way - just how my brain thinks when I am asked to beta something. :)

Like Reply

tomimt5 years ago(+1)

I think for beta testing both are equally important. It's important to see if you can actually complete the game with a various assortment of machines it is now currently being tested as well as how the game behaves when the player does something unexpected.

Like Reply

Burzmali5 years ago(+2)

Were this a beta test, I'd agree. but as the initial release was not completable, I'd say we are still in the alpha phase. No need to point out that the AM/FM switch is reversed in a car if the engine cuts out after a mile.

Like Reply

puckpanix5 years ago(+1)

I agree with this. This is not beta testing at all, or even alpha testing really. We're doing what amounts to QA testing that a software team would normally do before a release of any kind. QA testers have test cases to go through so they know what's broken and what's FAD. We don't need a "walkthrough", we need test cases.

Like Reply

itch.io

Viewing post in Walkthrough