This video will show you on the Mac, how to setup your Eclipse IDE to use Maven, TestNG, SVN, and Selenium. I will also quickly show you how to create a project and set it to use these tools.
More information and source code: http://jcwebconcepts.net/?p=409
Paul King presents some of the tools helping one programming in Groovy: Cobertura – code coverage, CodeNarc – code style, EasyB – acceptance tests, GroovyDoc – documentation, GroovyMock/Spock – mocking and testing, Hudson – CI builds, Maven/Ant/Gant/Gradle – build files, OSGi – bundles, and Spring/Guice – dependency injection.
San Francisco Java User Group presents Chris Bedford who talks about:
- How to write functional tests with Selenium (including explaining its IDE, architecture, RC, and alternatives like Canoo WebTest)
- How to set up Selenium testing for web apps in continuous integration using Maven, Ant, Cargo, etc.
- How to use Hudson for build server
The Maven team has gone to the ends of the earth to ensure backward compatibility, improve usability, increase performance, allow safe embedding, and pave the way for implement many highly demanded features. This talk will briefly cover the process and tooling changes that have occurred in the Maven project in order to accomplish what we have done with Maven 3.0, as well as discuss the architectural and feature changes. Some of the process changes include setting up a multi-platform Hudson grid, building out a framework of over 440 integration tests, creating integration tests for all core Maven plugins, and systematically seeking out Maven 2.x OSS projects to validate Maven 3.x’s compatibility. We also built out a framework that measures disk I/O, network I/O, memory consumption, and CPU utilization to ensure that performance doesn’t degrade.
Jason recently talked about Maven 3 at the Maven Meetup on March 19, 2009. Here is his entire presentation. In it, Jason discusses plans for Maven 3: support for incremental builds, changes to Plexus, better multi-language support, a queryable lifecycle, changes to the Plugin API, extensible reporting, a refactored plugin manager, project builder, and a new subsystem for interacting with repositories. You’ll hear Jason discuss plans to make Maven 3 more pluggable and to prepare for a Maven that can integrate with various repository formats. Jason also talks about changing the report generation subsystem to be more focused on report generation and integration with tools such as Sonar and Hudson.
Maven 2 is becoming increasingly popular in larger organizations looking to standardize and industrialize their build processes as well as in smaller shops simply trying to get more out of their builds. This session, for developers wanting to learn about Maven and Maven users wanting to get more out of their build tool, covers the main features and benefits of Maven and then looks at some of the more advanced uses of Maven in the real world, including complex transitive dependency management, dependency conflicts, multimodule projects, and integration with other build systems. It also looks at how the m2eclipse plug-in can be used to improve the Maven user experience and how to use the Nexus repository manager with the Maven release process to publish your APIs within your organization.
Martijn Verburg and Michael McCarthy guide the users through a whistle stop tour of Maven. Martijn describes Maven as a Java project management (life cycle) tool rather than as a simple build tool. It has a simple XML configuration model known as the Project Object Model to describe the dependencies and external modules a project utilises. Maven is explained to be capable of automatically organising these for the user, and drives forward the idea of compiling before testing, testing before packaging, and packaging before installation then finally deployment. Deeper into the talk, shows an example of a POM file and features Maven’s ability to give pre-defined targets for performing common tasks such as compiling code and the packaging. Maven is built around the idea of reusing build logic and standardising builds by preferring conventions over configuration.