To Shake!
The weekend was busy as any impending across-the-Atlantic move would demand but I managed to download Chrome (I have been using Firefox for years) and poked around the web.
I tried to run the technorati searches that we appear on but it didn't work. It may be a matter of sgining-in, the reading was interesting nevertheless.
Some of the posts were pro unit test other against, Agitar, Agile, etc.
A blogger explained that Agile is an incremental methodology where the developer decides what to work on next. A couple of them stated in other posts that a lot of their collegues just don't write unit-tests.
It is not surprising: as soon as the decision of what to work on is made by the over-pressured project manager, something's got to give.
Agitar's demise may be a consequence of the previous, but it also missed some crucial requirements: it just worked unit tests, the underlying framework was somewhat limited. It also solved just part of a customer problem: product quality. By only adding a lock statement the whole thing lost compass.
BTW, Chrome seems very useful...
Labels: agile, chrome, QA_Automation, unit_testing, Visual_Unit_Testing