Teams start in Experimental mode / Discovery mode
it's fun / fast / agile and test would slow things down
Write test to make sure we don't break something when we add new feature / refactor
The refacor breaks the tests, we loosing some speed
Spend more time maintaining the tests than the app
The developers loved phase 1, 2, but they hate phase 3 and the loss of fun / fast / agile and discovery mode is killing the moral
The fastest way to hell is
When you test the internals you are coupling
your test to your implementation and
not the application behaviour
The Surface, the Perimeter, the Contract rarely change and is independant from the implementation
Selinium / webdriver
Connection to DB / Services
There is a lot of Manual Testing
Every change on the UI breaks the Automated Tests
The most important Tests are taking
The unit test is written by the programmers for the programmers and it's not testing the running application
The majority of your Test efforts should be in
Unit Test testing the good behaviour of the Application
This is where the usecases, the stories, the senarios are express
This is where the behaviours of the app are express it's
the contract with the world
The communication is bi-directional
They figure out if we are expressing our self correctly to the outside world
A small number of test checking that everything works together nicely
Don't test the implementation it is
To certify that the implementation is correct