Posts
Showing posts with label Automation in agile projects. Show all posts
Showing posts with label Automation in agile projects. Show all posts
Why QTP is anti agile?
I want to make few points quickly in favor of that.
1) No support for programming languages like Java, .Net so that it allows it to be used as an acceptance testing tool.
2) VBSCript doesn’t help in everyone’s participation in the automation process, which is a key in agile projects.
3) No IDE support : QTP’s IDE is no way near Ideal hence makes maintainable a tough battle.
4) NO support for standard IDE like eclipse //
5) Multi browser support is limited/
6) Cant execute scripts on Linux and Mac platforms.
7) No continuous integration support, makes it rally tough to be used as an acceptance testing tool.
Twist GA - Update
Twist is going GA on 27th April.
Waiting eagerly for this release as it should be a much stable release. More feedback , once I give it a go..
Modern day webapps - How to approach automation testing
Web apps are getting complex with browsers getting rich in behavior at the same time diverse from diff browsers. Technologies like Ajax and J-query has given a new dimensions to web apps. But at the same time automation testing getting difficult with rich javascript pages .
How do one cope up with this. Multiple browser, different behaviors and rich client specific technologies to write and maintain tests.
Web automation needs to be maintainable and scalable, but how does one keep these factors in mind coping up with browser's incompatibility.
1) Select a tool which behaves with different browsers naively.
2) Write scripts driven by user behavior.
3) Avoid using browser specific object identification. (e.g> X- Path)
4) Keep scripts modular and small, so that its easy to write and maintain.
5) Don't hack the stuff to make something work (E.g> using javascript to do stuff - like cookie editing), I would rather avoid doing that, as brittle scripts may lead to serious disaster, especially in agile environment.
Automation Testing - Traditional to Agile
I always wonder, how the face of automation testing has changed over the years. Automation testing has always been perceived as post development, costly activity to be done by specialists.
Agile methodology has broken all the barriers/Myths of automation testing. From a heavy weight , System level , Regression oriented process to Acceptance oriented, all level light weight process.
In traditional projects, automation is only used as regression testing tool, and always perceived as to be done after "Stabilisation of the product"
Automation in agile projects becomes inevitable as its a mean to reduce the feedback cycle. it reduced the regression cycle, and helps producing quality code with higher pace. it also helps system to be robust all the time.
Unlike traditional project automation, which is only participated by specialist, in agile projects automation is practiced at all levels (Unit, System, Integration) by all stake holders of the project in one form or another.
In Agile methodology, automation tests are treated and take care as part of the overall source code. It needs the same love and care as any other piece of code in the project.
Automation in agile project is not just about automating the test cases, but automation is any mean to convert manual process to reduce the time waste or to add value in overall process.
Subscribe to:
Posts (Atom)