In Part 1 of this tutorial, we set up the CruiseControl Continuous Integration server against a Subversion repository. In this second part, we'll continue where we left off by taking our build results online with the CruiseControl reporting web application.
The purpose of this paper is to take a practical approach to automated software testing and explain reqirements for its success. To be successful one needs remember that there are four interrelated components that have to work together and support one another: 1) An automated software testing system based on one point maintenance and reusable modules, 2) Testing infrastructure consisting of the events, tasks and processes that immediately support automated, as well as manual, software testing, 3) Software testing life cycle that defines a set of phases outlining what testing activities to do and when to do them, and 4) Corporate support for repeatable processes.
Beehive is a new Apache project aimed at making J2EE programming easy. The controls sub-project provides a model for programming business functionality that leverages lightweight JavaBeans and declarative configuration through JDK1.5 annotations. This article presents a behind-the-scenes look at how controls are built. It examines the role of the annotation processor, artifact generation, and eventual control assembly. By understanding this process you will be in a strong position to understand how the control architecture works in general and to build advanced controls where the control client needs to be customized to the controls it uses.
This article covers some of the various types of automated developer tests you can run with every source code change. It provides examples of Selenium, DbUnit, and JUnitPerf tests that can help you discover application problems early -- that is, if they're run often.
Many Web applications use the Model-View-Controller (MVC) pattern to separate the three concerns. These applications frequently use PHP or JavaServer™ Pages (JSP) technology in the presentation layer. While those technologies are widely accepted and certainly effective, they do not represent a language-independent means of presentation. On the other hand, like Structured Query Language (SQL), XQuery is a lookup specification tied to the XML standard, which is language- and platform-independent. Using XQuery for presentation enables view-side developers to create robust presentation effects without tying the view to any particular underlying application server or programming language. In this article, explore the advantages of XQuery over other view technologies, how XQuery is implemented in the presentation layer, and a realistic example of such an implementation.
Significant performance issues are likely to arise even in well-planned applications. In this two-part article, Chris Grindstaff offers techniques for analyzing and addressing performance problems. In this first installment, you'll learn how to measure the performance of Eclipse-based Rich Client Platform (RCP) applications, determine if slowdowns are caused by CPU or I/O bottlenecks, and keep the UI thread idle to maintain responsiveness. Part 2 addresses memory problems.
Using open source tools for developing grid applications opens up a wealth of possibilities. The first is a very rapid development process, especially if you take advantage of script languages like Perl or Python and deployment environments like Apache. There is also a wealth of examples available that can help you. Examine the advantages and disadvantages of developing a grid solution using open source technology.
week, we will explore debugging PHP code with xdebug, the swiss army knife for PHP developers. In this article, we assume that you have xdebug installed on your system. If you haven't, the first article of the series explains how to install and configure xdebug. Debugging software is not exactly a fun job for developers. The most widely used debugger for PHP still seems to be a var_dump() statement, possibly in conjunction with die() to halt program execution at a certain point. While there is nothing wrong using var_dump() statements in itself, you still need to change the program code to debug a PHP script. And worse, after you have finished debugging, you must remove all var_dump() statements again (well you should, at least). It may well be that a few days later you'll find yourself adding the very same var_dump() statements to your code again because you need to go hunting another bug.
This article introduces using the Aptana RadRails plug-in for Eclipse, which allows Eclipse to become a first-rate Ruby development environment. Ruby developers who want to learn how to use the rich infrastructure of the Eclipse community to support their language will benefit, as will Java™ developers who are interested in using Ruby.