"Delete Account" says the button.

So I pressed it

"Continue ?"  - "Yes" or "Cancel"

Yes

Wonder what it did ????

Did it delete all records from the database ?

Just set a flag somewhere ?

Why wasn't it mentioned in the spec - did the programmer just decide to make it up ?

Does the customer really want a delete account button ? If so, shouldn't there be some extra safeguards around it ?

What happens when little Johnny plays with Daddys computer and deletes Daddys account ?

Been doing some exploratory testing of the program delivered at the end of Sprint1.

Supposedly the goal of Sprint 1 was to allow a user to securely log into an account

So why is there a "Delete Account" button ?

Time to give the programmers a lesson in Testing 101...

If they produce some sort of spec at the start of a Sprint then we can start to prepare test cases so that when they deliver the program we can start testing right away. Instead there will be a delay whilst we find out what this Delete Account button is all about.

If they mention in the spec that there is a Delete Account button we can think about the 'what ifs' and the risks such as the little Johnny scenario. Maybe a Delete Account button isn't such a good idea.

If they give us some sort of design spec then we would know what actually happens when the Delete Account button is pressed so that we can test to see if it really does what it is supposed to do.

Just follow a few simple procedures

Communication

No surprises when the program is delivered to be tested

And testing becomes more efficient and useful

Instead of a bottleneck and a whine festival

Now where's that Delete Programmer button...