I use Selenium WebDriver to test the UI in integration tests.
I use Jenkins to trigger build and deployment when a commit is made to the code repository. Cobertura or Clover code coverage reports are generated with each job. I also use the Deploy and Publish Over FTP Jenkins plugins as well as the Execute Shell build task with some Jenkins jobs.
I've worked on several projects using an Agile development methodology. One of the projects went through a lot of changes and working incrementally allowed the team to keep up with the changes. Even on projects that aren't fully Agile, I still have my own scrum board and update my lead each day with an email stating what I did yesterday, what I'm doing today and what my blockers are. After working in teams adopting Agile metrology it's hard to work differently
I use JUnit 4 for unit tests and to invoke Cucumber integration tests.
I use Mockito in unit tests where the SUT interacts with collaborators that can't be tested in isolation. On a recent project the code had to be refactored to make it testable, removing invoking of collaborators in the SUT with dependency injection. Mockito has origins in EasyMock, but the syntax is simpler and it supports BDD type syntax.
I've worked with Java since the early 2000's including a stint with Microsoft's J++. I have used Java to create business process servers, standalone Java applications, and Java based web applications.
I use Hibernate in web applications for mapping Java classes to database tables and data query and retrieval facilities.
View my LinkedIn profile. Please read my recommendations.

View Beverly Hill

View my Github resume or see my code example repositories on Github.

My Github repos

As part of an Agile team, I use Rally to manage project work. I use a Rally Eclipse plugin to update Rally tasks directly from Eclipse.
I use Cucumber-Jvm for integration tests. These tests are run in specific Jenkins jobs following a job that does a compile and runs unit tests.
I have installed and configured WebLogic 9 for development staging and managing development deployments.
I use Jetty standalone to test web applications during development, and embedded in integration tests that are automated.
I have used Tomcat to test web applications during development.
I use Maven for building and deploying web applications.
I use JQuery on this website for the mobile version.
I use Git locally and Bitbucket, Beanstalk, and Github for remote hosting. I use eGit Eclipse plugin, command line, SourceTree, and Tower to interface with Git repositories.
I have used SVN for many years with enterprise software development using Subclipse Eclipse plugin and Tortoise.
I use the eCobertura Eclipse plugin to check my unit test coverage during development. This is particularly handy when I've had to add unit tests to legacy code that didn't have any tests. I use the Jenkins Cobertura plugin to produce coverage statistics for management.
I use MAMP which is an integration of Apache server, MySQL dataserver, and PHP server side scripting to do development testing of web applications.
I use Clover as an upgrade from Cobertura to produce more detailed unit test coverage in Jenkins builds. I also use the Clover Eclipse plugin to see code coverage levels during unit test development. Clover's Eclipse plugin also produces Html reports that provide a lot of details on a projects's unit test coverage.
I used an Eclipse plugin for Team Foundation Server. TFS provides a lot of enterprise level functions for developers including easy management of branches and a project management-like system of associating work items with code commits.
I have used Ant scripts to compile and test projects and also for utility type work such as copying/moving log files and making file backups.
I try to automate everything and Unix shell scripts have served me well with automation. I've automated entire business process servers, reporting and notification systems, read, processed, and transmitted files with shell scripts. Currently I use the Execute Shell build option in Jenkins jobs to execute numerous Unix shell scripts involved in builds.
I started learning Objective-C in 2008 after I got my first iPhone. I made a universal iPhone/iPad application that maintains URL lists and post the code publically on Github.
My first use of Sybase was in conversion from MS Access native data to Sybase dataserver. I've used Sybase as the dataserver for business process servers, Java desktop applications, and web applications. I have knowledge of table/trigger/view creation, SQL scripting, and indexing.
I've used MS SQL Server as the dataserver for desktop applications and web applications. I have used Microsoft SQL Server Management Studio IDE for database management.
I've used the Spring framework with Java web applications. These applications used Spring IOC, MVC, and transaction management.
I have used the iBATIS data mapper in the persistence layer of Java web applications.
I have been involved in many projects that were developed with the Waterfall methodology. In these projects I have performed in project management, systems analysis, and development roles.
I use the Eclipse IDE for Java development. I have used Eclipse for local and remote debugging, for test first development, and I've used many of the plugins including eGit, eCobertura, and Subclipse.
I use Xcode for iOS development. I also use the Instruments and iOS Simulator developer tools. I write unit tests in Xcode using SenTestingKit.framework and use Instruments Automation for UI application testing.
I use the CodeCover Eclipse plugin to monitor unit test coverage during Java development when a Clover license isn't available. CodeCover has more views and statistical data than Cobertura.
I have used Jira for issue tracking and for Agile development with the Greenhopper plugin. Using Jira issue numbers in commits, commit message display in the issues.
I use Coda 2 as the IDE for developing HTML 5 websites that do not have Java components.
I use TeamCity as a local continuous integration server for this website. I can run integration tests with changes in IntelliJ IDEA before commiting to SVN. After commiting to Bitbucket, the same integration tests are run locally on a MAMP deployment, then on a Vagrant VM with a clean clone from Bitbucket.
I use Vagrant/Virtualbox to create a new VM to run integration tests for this website.