0 Replies Latest reply on Jul 16, 2010 2:08 AM by Andrew Rubinger

    Test Automation Framework integration w/ Arquillian

    Andrew Rubinger Master

      Had the beginnings of an exchange this week with Walter White, who's writing a test automation framework.  Bringing our initial discussion public for others to weigh in:






      I noticed you forked my code :). This is very much incomplete - started phase 2 which is capturing more data and persisting it via hibernate to a database as well as using CDI / Weld for DI / IoC.

      I plan to release a bit more code (my other internal projects) and re-structure this, so I will have new code up shortly, perhaps a week or so. I don't know if this is readable enough, but I wanted it to get out there for review.

      Let me know your comments.





      Hey Walter:

      Yep, we try to be pretty proactive about finding good integration opportunities for ShrinkWrap/Arquillian.

      I haven't yet had a chance to dig in, but was hoping to get some overview of the problems you're trying to address. What's your elevator pitch for the project?






      I want to automate testing as much as possible. Developers seldom run performance tests, when they do, they're out of date (not synced with their unit / integration tests), why not use the same (less stuff to maintain). Many pages use the same widgets throughout the application, why not define an interface to interact with them and re-use that throughout the tests again. Some patterns are common to webapps (search, edit, delete, ...).

      Providing a suite to make this happen will ensure applications that are deployed have been more thoroughly tested. Developers can spend less time writing support code for tests and work on the actual tests themselves.

      Right now, my target is automating UI tests.
      1. more extensive UI integration testing (integrated load testing, spelling, CSS, HTML)
      2. validate deployments (through use of smoke tests)
      3. configurable depth of tests
      4. historical view (performance, errors, ...) / extensive data collection, eventually reporting
      5. pluggable authentication modules / operators

      That is a rough overview, I have many more ideas that I'd like to work on after I get phase 2 up and running which is a ways out.