Selenium is an open source project with no formal guidance, making problem investigation time-intensive for testers. This article provides best practices for common issues during testing based on Selenium 1.0, which was released in June 2009.

Selenium is a tool for writing automated tests of web applications. You can develop automated tests in the programming language of your choice such as c#, java, python, php, perl and ruby as well as running those tests on different combination of browsers such as Chrome, Firefox or IE.

WaveMaker imports a database schema and automatically generates corresponding Hibernate classes. Chris Keene describes how to use WaveMaker to automatically generate Hibernate classes, including an example of how it works in practice.

Is your software architecture what you think it is? The designs we communicate to each other aren't always what we expect when it comes to source code. Paul Duvall returns from his hiatus in this installment of Automation for the people to demonstrate how you can discover architectural deviations by writing tests using JUnit, JDepend, and Ant to discover problems proactively instead of long after the fact.
Of the many software development projects I've worked on and observed, one thing is almost a constant: The architecture you think you have is often different than what you actually have. Analyzing code metric reports, like those created by tools such as JDepend (see Resources), can be effective in determining if your code adheres to an established architecture. Some teams reverse-engineer their code into UML diagrams for the same effect, and others even use an IDE that generates these same artifacts while coding -- real-time reverse-engineering. Yet, all of these approaches are still reactive. You must manually review and analyze a report or diagram to determine an architectural violation, which in some cases could be long after the fact.

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.

Databases are often out of sync with the applications they support, and getting the database and data into a known state is a significant challenge to manage. In this installment of Automation for the people, automation expert Paul Duvall demonstrates how the open source LiquiBase database-migration tool can reduce the pain of managing the constant of change with databases and applications.

Load testing is often relegated to late-cycle activities, but it doesn't need to be that way. In this installment of Automation for the people, expert Paul Duvall describes how you can discover and fix problems throughout the development cycle by creating a scheduled integration build that runs JMeter tests.

Managing source-code dependencies among projects and tools is often a burden, but it doesn't need to be. In this installment of Automation for the people, automation expert Paul Duvall describes how you can use the Apache Ant project's Ivy dependency manager to handle the myriad dependencies that every nontrivial Java™ project must manage.

Although many development teams use version-control systems to manage code changes, they can struggle when developers code off the same code base, in parallel. In this Automation for the people installment, automation expert Paul Duvall shows how to effectively tag, branch, and merge source code using the open source, freely available Subversion version-control system.

Automated builds aren't just for development teams — they can be extended to facilitate moving software from development all the way into production. This article describes how to use Ant with Java™ Secure Channel for remotely deploying software into multiple target environments.