Discussions

News: A J2EE Testing Primer

Bookmark and Share Get thread feed

  1. A J2EE Testing Primer (3 messages)

    Scott Ambler explores several best practices for testing J2EE-based software and describe how to organize your environment to support effective software testing.

    Read A J2EE Testing Primer.
    Reply to this

    Threaded Messages (3)

  2. A J2EE Testing Primer[ Go to top ]

    Hey Scott, you forgot Cactus in your article .... :)

    For those interesting in testing J2EE applications, Cactus is a framework for unit testing server side java code. It is available at http://jakarta.apache.org/commons/cactus and is part of the Jakarta Commons project from the Apache Software Foundation.

    In it's current status, it lets you unit test Servlets and standard java classes that uses Servlet objects and simple JSP taglets. Work is under way to provide support for unit testing of EJBs and Servlet Filters. Check the goals and status web page for details at http://jakarta.apache.org/commons/cactus/goals.html (it gives an overview of J2EE unit testing problems and how Cactus would solve them) and http://jakarta.apache.org/commons/Cactus/scope.html (the scope page explains how to test the MVC model and gives the current status of Cactus in regards to this).

    The goal of Cactus is to encompass as much as is physically possible the full spectrum of J2EE in order to provide unit testing for it.

    Cactus is also very much XP oriented in that it provides custom Ant tasks and build scripts for major servlet engines in order to automate unit testing of J2EE applications, in the XP continuous integration fashion.

    Thanks.
    Vincent Massol.
    Reply to this Reply to original

  3. A J2EE Testing Primer[ Go to top ]

    Does anybody know of any use case based testing tool for web based applications? This article talks about tools for testing components, and as far as I know, unit testing is useful for testing single classes or even components. I think it would be very useful to be able to "record" a valid interaction with a system (a complete use case), and use it later as a regresion test as the system evolves. This would test the system as a whole, that could be useful to make integration tests and to see if the system fits user requirements, instead of testing it in little pieces, that could be useful to locate possible bugs.
    Reply to this Reply to original

  4. A J2EE Testing Primer[ Go to top ]

    Wow - where's the beef? That's like, testing 101.
    Reply to this Reply to original