By rick
via blog.objectmentor.com
Published: Jan 04 2010 / 22:52
It happens over and over again. I visit a team and I ask about their testing situation. We talk about unit tests, exploratory testing, the works. Then, I ask about automated end-to-end testing and they point at a machine in the corner. That poor machine has an installation of some highly-priced per seat testing tool (or an open source one, it doesn’t matter), and the chair in front of it is empty. We walk over, sweep the dust away from the keyboard, and load up the tool. Then, we glance through their set of test scripts and try to run them. The system falls over a couple of times and then they give me that sheepish grin and say “we tried.” I say, “don’t worry, everyone does.”
-
Jonathan Ive interview: Apple's design genius is British to the core
-
CSSDeck Version 2
-
Mojito - Yahoo's NodeJS based Multi Device Application Framework
-
VMware vFabric Suite 5.1 Standard and Advanced Editions Now Available for Download
-
Object Pipelines (C#)
-
Improving the quality of large legacy codebase by incrementally enforcing encapsulation – Matej++
Comments
Topnotch replied ago:
Simply put you almost NEVER want to script a GUI if there is another alternative. It's better to script a CLI (command line interface) instead for any kind of automation. Be it tests or tasks.
Voters For This Link (11)
Voters Against This Link (0)