aspose file tools*
The moose likes Agile and Other Processes and the fly likes In which tool do you construct your System Test Suite for web applications? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » Agile and Other Processes
Bookmark "In which tool do you construct your System Test Suite for web applications? " Watch "In which tool do you construct your System Test Suite for web applications? " New topic
Author

In which tool do you construct your System Test Suite for web applications?

Kent Chan
Greenhorn

Joined: Jul 12, 2009
Posts: 10
As we know, automatic test suites can help us a lot if we adopt XP.

There are two kindes of test suites, one is unit test suite written by programmer, the other is system test suite written by system testers.


Unit test suite can be implemented by JUnit easily, but how about system test suite? I'm looking forward to your answer.
David Newton
Author
Rancher

Joined: Sep 29, 2008
Posts: 12617

I use both Selenium and HeavyWatir, a custom Watir extension.
Kent Chan
Greenhorn

Joined: Jul 12, 2009
Posts: 10
It's said that functional test cases are time-consuming to write and very fragile to react to new features on the web pages.

1. How much time do you spend on writing and mainting these test cases ?
2. Do you feel frustraited if you have to change the test cases a lot ?
David Newton
Author
Rancher

Joined: Sep 29, 2008
Posts: 12617

Kent Chan wrote:It's said that functional test cases are time-consuming to write and very fragile to react to new features on the web pages.
This depends on many factors. The biggest keys for me were using the Selenium IDE to create the skeleton code, making sure my HTML was marked up in a meaningful way, and testing for the smallest amounts of functionality possible.

Kent Chan wrote:1. How much time do you spend on writing and mainting these test cases ?
Depends. Ideally I maintain them as little as possible. Things like Cucumber, and even relatively simple DSLs built on other products, make functional tests easier (if not easy) to write for non-developers, making it possible for QA departments to play a stronger role in the acceptance testing process.

The more semantically-meaningful markup I generate the easier testing can be--and the simpler the web page is the easier it is to test. Fortunately, the simpler the web page is the easier it is for the user to deal with.

The biggest issues for me have usually centered around Ajax, but if I'm only running a small number of tests when I'm developing, and using a continuous integration machine for full suites, it generally hasn't been *too* bad.

Kent Chan wrote:2. Do you feel frustraited if you have to change the test cases a lot ?
Of course.
Kent Chan
Greenhorn

Joined: Jul 12, 2009
Posts: 10
Sounds Cool.

Another question, you said you only maintained a small set of test cases. Wouldn't that lead to poor coverage?
David Newton
Author
Rancher

Joined: Sep 29, 2008
Posts: 12617

No, I said that I keep the functionality I'm testing as isolated as possible, and that when I'm developing I run only a small number of tests--relating only to what I'm working on at the moment. I might run the full suite only occasionally, or rely on the CI server to run the full suite.
Kent Chan
Greenhorn

Joined: Jul 12, 2009
Posts: 10
Got it! Thanks!

David Newton wrote:No, I said that I keep the functionality I'm testing as isolated as possible, and that when I'm developing I run only a small number of tests--relating only to what I'm working on at the moment. I might run the full suite only occasionally, or rely on the CI server to run the full suite.
 
 
subject: In which tool do you construct your System Test Suite for web applications?