Last active
August 29, 2015 14:10
-
-
Save paulghaddad/84aef25e0b8d9ead512b to your computer and use it in GitHub Desktop.
Level Up 3: Knows why manual testing doesn't scale
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1. Name some cases where manual testing is preferable or necessary to verify code. | |
Manual testing is essential for usability testing. This should be performed with real users, under real environmental conditions. This form of testing looks at human factors: is the software easy to use? | |
2. Name some strategies for manually testing code that constrain the time cost of testing | |
To limit the amount of time spent manually testing, the tests should be performed frequently and as early as possible during each iteration. This pinpoints problems early, where they can be fixed more easily. If these tests are conducted at the end of a project, you may find problems that take a lot of time to fix, lead to many additional iterations, and thus tests--and time--in the future. Another technique to constrain the time spent on testing is to use Timeboxing, which enforces a set period of time on an activity, in this case, testing. Before starting, a time limit is agreed upon, and once reached, testing stops. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment