Testing - Pt 1

I love automated testing. In a rare diversion into op-ed1 I thought a put few thoughts (read - opinions) together.

Before I start on how best to compose your tests, I briefly ask - What are the reasons for testing? Broadly, I think they are:

  1. Reduce total number of bugs / increase product stability
  2. Ensure software works as per specification
  3. Achieve the above at low cost, low impact.

I think this boils down to providing software that does what your customer wants (features), doesn't do what they don't want (bugs), and do it without making too much noise (cost).

On to part 2 →

 http://en.wikipedia.org/wiki/Op-ed - "and thereon I decided to print opinions, ignoring facts."

Tags

ant (2)   antlr (1)   applet (1)   apsectj (1)   asm (1)   aspectj (1)   bdd (1)   blog (1)   cd (1)   coldfusion (2)   concurrency (4)   cucumber (1)   dashing (1)   docker (3)   drop-wizard (1)   drupal (1)   dsl (1)   gatling (1)   geb (1)   gist (13)   git (1)   graphite (1)   groovy (2)   hibernate (2)   ioc (1)   java (44)   java-8 (1)   java-fx (1)   jmeter (2)   jpa (2)   junit (5)   links (12)   maven (12)   middleman (2)   mocking (1)   mongodb (1)   oped (9)   os-x (1)   performance (4)   photos (1)   plaf (14)   ruby (3)   scala (1)   selenium (4)   software (10)   spring (5)   spring-mvc (1)   swing (15)   testing (17)   tips (4)   tomcat (3)   tuples (1)   tutorial (1)   unix (6)   vagrant (2)   web (4)   windows (1)