Finding bugs

1. Finding bugs
 - One characteristic of high quality in Software Systems is absence of errors (bugs)
 ( http://melancholy8914.blogspot.co.uk/2017/01/software-quality.html )
  => Eliminate them!
  => How? try to avoid creating them in the first place / try to find them before they cause trouble

2. Testing
 : a process of executing a programme with the intent of finding faults
 e.g. Black box testing, White box testing, Grey box testing

 1) Testing plan: Decisions and judgements about testing
  => Continue until you are finding no more bugs?

 2) Automation: particularly popular in OO development e.g. JUnit
  (+) Fast and easy: once setup, running and re-running requires an absolute minimum of effort from the developer
  (+) Consistent: each test is run in exactly the same way every time
  (-) Unsuitable for some types and classes of test
  (-) Consistent: running a test by hand may lead to a failure which the automated system doesn't uncover

 3) Coverage: a measure of what proportion of code is being exercised by testing

 4) Artificial bug insemination: a technique for estimating number of residual bugs in a system
  - Assumption:
   * bugs found are fixed (!)
   * bugs are evenly distributed (80/20 rules)

http://istqbexamcertification.com/what-is-a-software-testing/