Mock JDBC driver not worth it

Posted by: Michael Slatterys Weblog, on 02 Nov 2005 | View original | Bookmarked: 0 time(s)

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
Category: XML | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 1051 | Hits: 29

Similar Posts

  • Moq 3.0 RTM!!! more
  • Making WCF services amenable to testing more
  • Making WCF services amenable to testing more
  • Mocking indexer setters with Moq more
  • Making extension methods amenable to mocking more
  • Making extension methods amenable to mocking more
  • Linq to Mocks is finally born more
  • Moq 3.0 RTM!!! more
  • Don't be afraid of complex constraints more
  • Successive Method Calls With MoQ 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