Mock JDBC driver not worth it

Posted by: Michael Slatterys Weblog, on 02 Nov 2005 | View original

I think mocking DAOs is better than mocking a JDBC driver. A while back I wrote a blog entry that described an initial design of a JDBC driver that would be useful for mocking. It would use a cache stored in XML format. It would even support insert/update/delete (by having multiple cache 'states'). I put off writing the driver and instead used HSQLDB + DbUnit. It worked ok, but I was not satisfied with performance and the startup time of Hibernate. I was also too lazy to implement the driver...

Advertisement
The leading UI suite for ASP.NET - Telerik radControls
Outstanding performance. Full ASP.NET AJAX support. Nearly codeless development.

Similar Posts

  • Using Rhino Mocks To Unit Test Events on Interfaces more
  • Printing from Windows XP 64 bit to a HP LaserJet 5100 Series more
  • Rhino Mocks are strongly typed. Refactor unit tests with ease - level 200 more
  • JDBC 2005 Beta 2 Data Coercion [Angel-Saenz Badillos] more
  • My Blog Is Worth... more
  • Design for a Mock JDBC Driver more
  • MySQL Data truncation Error more
  • JDBC 2005 Beta 2 Data Coercion [Angel-Saenz Badillos] more

News Categories

.NET | ADO.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Community Server | dasBlog | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD