Test scripts? What’s the point?

Do we still need:

1. Go to login page ----- Login page is displayed

2. Enter username into username field: John ----- Username is displayed in username field

3. Enter password into password field: Secret ----- 6 asterisks are displayed in password field

4. Click on login button ----- Login button is disabled

5. Home screen opens

…

Really? What's the point of this 20 years into the 21st century?

30 years ago there used to be two reasons for writing this sort of test script:

1. Allow somebody else to review it, check that it covers everything needed

2. Serve as instructions for executing the test, especially as part of some sort of regression

Things have moved on since I used to print off reams and reams of paper, initial every step, sign at the end of the script and then neatly file everything in a massive ring binder, never to be seen again. These days I am not sure where to find a ring binder in my office.

In a world where increments of functionality to be implemented (user stories) are getting smaller and smaller and developers and testers are working closer together, the need for spelling everything out in intricate detail is shrinking. In a world where everyone is trying to move through the develop, test, deploy cycle as quickly as possible, there is no time for writing long test scripts, never mind big long reviews.

In a world where automation tools are everywhere, anything that will be executed more than once is scripted in code.

So what’s the point of a manual test script?

There isn’t one.

If it needs executing more than once, automate it.

If you need evidence of what was tested, record what you are doing.

Save the trees and your sanity!