Here’s a challenge.
You’re sitting down designing some tests.
Can you describe them in 5 words or less?
Here’s a challenge.
You’re sitting down designing some tests.
Can you describe them in 5 words or less?
Explore profile page with CRUD.
Click everything twice, observe database.
Match user actions to logs
Journey, there and back again
3 words;
Now I’ve got 2 words spare for automation.
Goldilocks goes to test town.
What would cause an error?
How can someone perform an ‘unexpected action’?
The person testing knows what action they want to do, but doesn’t know the outcome. They don’t know what the software can handle or was intended to handle.
I would put it like this:
Perform an action that they assume the software might not handle as they assume it should.
Experience as a user would
I only had 5 words
A user can perform an unexpected action in software. Think of a game where you might be able to glitch out the level - that’s an unexpected action, they might have done it intentionally or not, but it’s still unexpected.
Further;
We don’t know what the software can handle but we should know what its expected to handle. So we do something unexpected instead.
Simplest example is entering numbers into a first name field or something like that.
what do the requirements say
What do the users need
Delete default values and proceed.
Break the connection
Remove rights and/or roles
Try some combinations