we use accetance written in Concordion (http://www.concordion.org/) to drive all development stories in our agile shop.
Acceptance tests are written by the tester and the business first then passed to the developers for implementation (there's usually a lot of backwards and forwards to get the write level and format of these tests in the beginning). The acceptance tests usually talk to a fixture layer which communicates either internally with the app, via queues, web services or web gui using htmlUnit. The whole suite of acceptance tests can take from 10 minutes for some teams to 6 hours for others! Some projects spend alot of time trying to keep these times down but I believe that sooner or later you will not be able to stop them growing in size as the app grows. One of the teams came up with a good solution for their multi-hour acceptance build. They divided up their suite into 6 'slices'. Each slice takes about 30 minutes to run but they actually run in parallel on the build machine. This means you will be notified of a failure much sooner than one big build. Unfortunately, our emphasis on acceptance tests means that sometimes we do not have the best unit test code coverage so we tend to run the acceptance suite before check in. My team's plan is to get back to basics, improve our unit test code coverage so that we feel comfortable just running all the unit tests and the current acceptance test (perhaps some related ones using the group functionality of TestNG) before check in and let the build agents catch any other failure in the whole suite. Hopefully, failures will be rare if we design the app right(!) Another tactic discussed is to create a suite of acceptance tests that cover a good selection of them without taking too long to run and have those run before check in. A 'smoke test' group in TestNG. HTH R. On Sat, Feb 14, 2009 at 11:39 PM, JW <[email protected]> wrote: > > I've already recommended FEST to the Swing team. I think that was the > one that could use groovy which I thought was cool. It will be > interesting to see what the Swing team eventually ends up using. > > On Feb 14, 2:56 pm, Alex Ruiz <[email protected]> wrote: >> Hello Jason, >> >> I recommend FEST (http://fest.easytesting.org/swing) for functional >> testing of Swing UIs (disclaimer: I'm the creator.) The project is open >> source, under Apache 2.0 license. We released version >> 1.0<http://www.jroller.com/alexRuiz/entry/fest_swing_1_0_gui>last >> month and we are currently working on version 1.1. >> >> Now the marketing pitch :D >> >> FEST provides a compact and yet readable API that reads as a specification. >> For example: >> >> dialog.comboBox("domain").select("Users"); >> dialog.textBox("username").enterText("leia.organa"); >> dialog.button("ok").click(); >> dialog.optionPane().requireErrorMessage() >> .requireMessage("Please enter your password"); >> >> It also provides useful features that help test writers troubleshoot test >> failures: >> >> * Failure to look up components include the component hierarchy in the error >> message >> * Screenshots of the desktop embedded in the HTML test reports >> >> FEST can be used with JUnit or TestNG. >> >> I hope that helps. I'm not sure FEST is what you are looking for :) >> >> Best regards, >> -Alex >> >> On Sat, Feb 14, 2009 at 9:04 AM, JW <[email protected]> wrote: >> >> > Hello All, >> >> > We've just started our agile process for this new project. I'm using >> > Hudson to track our TestNG tests. I plan on having the developers use >> > a TestNG profile specific to those tests that run slower -- these will >> > most likely be for acceptance tests. These are the black-box, system- >> > level tests that they'll need to write for each iteration. We have a >> > web application and also a Swing GUI. Is anyone else automating these >> > acceptance tests required for agile iterations? What tools have you >> > found helpful for developer acceptance tests of Swing GUIs and are >> > such tests harnessed in TestNG? Does your QA group expand on the >> > tests using the same set of tools or not? >> >> > Thanks in advance for your reply. >> >> > Regards, >> >> > Jason Weden >> > Senior Software Engineer >> > Motorola, Inc. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
