If you have been happily using Easymock for the past years, this blog post is for you. Because you need to upgrade to Mockito, the new kid on the block in the mocking universe. Why bother about what mocking framework you’re using to create your unittests? Because it will improve you tests, make them more expressive, and help you write better code. Read on if you want to know more. Read the rest of this entry »
Posts Tagged ‘Testing’
Easier mocking with Mockito
August 13th, 2009 by Rob van Maris(http://blog.jteam.nl/2009/08/13/easier-mocking-with-mockito/)
Automated functional testing with WebDriver
August 5th, 2009 by Roberto van der Linden(http://blog.jteam.nl/2009/08/05/automated-functional-testing-with-webdriver/)
There is nothing nicer than having a functional test suite that checks if your application is still working as it should. It is even nicer to run these tests and see what is happening, while the tests are being executed. Two of the tools that give you this opportunity are Selenium RC and WebDriver.
In the project that I’m working on I use WebDriver to create functional tests. In this post I will try to give you an impression of why we switched from using Selenium RC to WebDriver and how we used WebDriver to test a Content Management System (CMS) and helped us making understandable tests.
Performance testing a Flex BlazeDS application
July 14th, 2009 by Rob de Boer(http://blog.jteam.nl/2009/07/14/performance-testing-a-flex-blazeds-application/)
In the past few years I’ve seen an increasing interest in Flex applications at our customers. I have to say that I’m not surprised about this trend. Not only do Flex applications generally look great, but they also provide a big boost to user experience. As a developer and architect I am also quite pleased with the programming model and extensive widget library. Sure, Adobe can still improve on a lot of things, but so far I have always worked with pleasure on Flex applications.
Read the rest of this entry »
Testing with factories
July 10th, 2009 by Tom van Zummeren(http://blog.jteam.nl/2009/07/10/testing-with-factories/)
On July 1st, Jelmer added a very useful blog post about testing the database layer in which he suggested to use “insert statement” and “fixture” classes to provide a good way to insert test data into your database. I am also using that technique as I’m writing unit tests for the database layer. I have to say this really makes unit tests less work to write, more focussed and therefore more fun to write!
Although this technique solves the challenges we have in database layer tests, we might encounter similar challenges when writing unit tests for other layers (such as the service or frontend layer). This is because such tests often also require “test data” you need to create. Only this time the test data is not in the form of database rows, but in the form of Java objects. Such objects need to be instantiated in a valid state and often depend on other objects. I find this quite similar to inserting rows into database tables having not null columns and/or foreign key constraints.
Read the rest of this entry »
Testing the database layer
July 1st, 2009 by Jelmer Kuperus(http://blog.jteam.nl/2009/07/01/testing-the-database-layer/)
The database is an integral part of many applications and writing queries is often hard. For that reason I have always written integration tests for the data access objects or DAO’s that I use to access the database. The way I write my DAO tests has changed a lot over the years and in this post I’d like to document the ways in which it has changed and why.