The perils of GUI automation as revealed in Shakespeare's tragedies.
Of Dictionaries and Tables : Why your Domain Specific Language needs a Dictionary
Endur/Findur Upgrades : If I were you, I wouldn't start from here
Test Automation For Endur/Findur : Part 3 - An example-based introduction to SpecFlow
Testing with large datasets - can't see the wood for the trees?
In the beginning there was Cucumber (or the Genesis of SpecFlow)
Test Automation for Endur/Findur : Part 2 - Beyond Unit Testing
In Endur, automated unit testing is necessary, but not sufficient. Not by a long way.
In this post I look at the effort/reward pay-off for automated testing and why unit testing and automated system testing have quite different profiles. If you recognise why, it becomes easy to see why so many attempts to automate Endur testing end in failure, but also provides the clues necessary to make it a success.
Test Automation for Endur/Findur : Part 1 - Where the bodies are buried
Inverse scope creep
Most people's idea of regression testing a trading system is "if the P&L is the same, then we haven't broken anything".
That's not true and it's not good enough. We introduce the concept of inverse scope creep to explain how this impoverished approach to testing allows functionality to atrophy over time and is literally a waste of money.
Those Three Little Words (or how to design a specification language)
Those 3 little words. No, not those 3 little words....Given/When/Then.... it sounds so easy, but what exactly does it buy you? Answer: not a lot. Not without a substantial intellectual effort on your part. You to have to design a language; a language for specifying behaviour.
We present 5 tips to get you started.