Skip to content

Instantly share code, notes, and snippets.

@lawrencewalters
Last active August 29, 2015 14:07
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save lawrencewalters/9bcdca3f499756ce3da3 to your computer and use it in GitHub Desktop.
Save lawrencewalters/9bcdca3f499756ce3da3 to your computer and use it in GitHub Desktop.
It's Not All Automatic

It's Not All Automatic

Knows why manual testing doesn't scale

Name some cases where manual testing is preferable or necessary to verify code.

When visual design changes are made - it's exceedingly difficut to validate design changes automatically, especially when they don't impact the functionality.

Usability - if usability is important (it always is), an automated test won't tell you if you've made some changes that hurt it (like creating a div that hides buttons or links - the machine tests are not going to realize this)

Name some strategies for manually testing code that constrain the time cost of testing.

Having people with otherwise free time, or who are between tasks or blocked waiting for something else to do their "regular" job perform tests. Time boxing the tests, as well as training the testers to look for specific things that we know the automated tests won't cover (like layout). Also, not giving testers complete scripts can maximize their effectiveness - meaning that they are more likely to exercise the system in ways we have not thought of, which will more effectively cover the application and turn up previously unknown issues at a higher rate than following a script.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment