Automate Testing

[forums-5]

In Step2 of article "Testing: You don't have to be Agile to be agile " you've mentioned that :
"
Don't test via the GUI unless you are checking the GUI. Rendering screens and web pages takes a lot of time, testing via an API or a headless browser will be dramatically faster.
"

i wonder how u use these tools to automate the test without working as "record/play back" ?

article link "http://blogs.atlassian.com/developer/2009/08/testing_and_agile_software_development.html"

your help highly appreciated
--
Post by knight - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=38477
_______________________________________________
Jira-user mailing list
Jira-user@...
To unsubscribe or change your options visit this page:
http://lists.atlassian.com/mailman/listinfo/jira-user

[forums-5]

We write our automated tests in Java instead of recording them with a tool via a browser. We use  [JUnit|http://www.junit.org/] to run our tests and for those tests that require a headless browser, we use [HtmlUnit|http://htmlunit.sourceforge.net/] to provide this. Both JUnit and HtmlUnit homepages contain links to documentation on how to get started with them as well as their JavaDocs. HtmlUnit is also used as the underlying browser by a number of open source test tools, so if you prefer Ruby to Java you can use [Celerity|http://celerity.rubyforge.org/] or [Canoo WebTest|http://webtest.canoo.com/webtest/manual/WebTestHome.html] if you prefer Groovy. The HtmlUnit homepage lists other options as well.

Andrew Prentice
--
Post by Andrew Prentice - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=38477
_______________________________________________
Jira-user mailing list
Jira-user@...
To unsubscribe or change your options visit this page:
http://lists.atlassian.com/mailman/listinfo/jira-user