current community

your communities

more stack exchange communities

Stack Exchange
tour help
Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.
up vote 0 down vote favorite

We have an application with Oracle backend. The DAO layer is written in C# and uses nHibernet to perform the data operations.

To unit test our DAO code, we use SQL Lite which creates the database based on our existing mapping in the project.

Some of our nHibernate queries that go to oracle use (+) for outer joins. Now SQL Lite doesn't understand (+).

There can be some more syntax from Oracle that SQL Lite doesn't understand. How do we fix problems like these?

What are the other database systems that can be used for unit testing the application code.

share|improve this question
    
You can either unit test using an Oracle database (sort of a contradiction), or avoid the SQL that SQLite doesn't understand. There aren't going to be any other databases that understand the Oracle-specific code. Why don't you use integration tests to cover the Oracle-specific code? –  Robert Harvey Dec 11 '13 at 21:54
    
Why would you not test against the dbms you are targetting? –  GrandmasterB Dec 11 '13 at 22:10
    
This is an existing application and an existing framework –  dineshsbisht Dec 11 '13 at 22:16
    
Why not change your outer joins to use the standard syntax? Of course there still may be Oracle-only features that you use. –  kevin cline Dec 11 '13 at 23:10

2 Answers 2

up vote 1 down vote

Testing against a different DB than the one you're going to use in production isn't going to give you any benefits. What's the point? Some of your tests might pass against SQL Lite but fail when connected to oracle. Worse than useless.

So you've got two choices:

  1. Mock out your DAO layer, so that your code doesn't actually talk to a DB, and thus making them "real" unit tests. Now you are actually testing your c# code and not the DB nor nhibernate.

  2. Connect to another Oracle DB (eg, a UnitTesting DB with dummy data in it) and test against that, which would be my preferred choice. The TDD nazi's will scream at you "it's not a REAL UNIT TEST" to which I'll answer "I don't care what it's called, it's testing my code which is what I need".

share|improve this answer
    
I like both choices. I wish I could do the first one.. but I am still learning unit tests and can't modify a lot of DAO code. I think the second is seems more doable at this point of time. Thank you! –  dineshsbisht Dec 12 '13 at 14:53
up vote 0 down vote

I wouldn't consider needing a database as part of the test to be unit testing. That's more like integration testing. A unit test shouldn't need something external to the method being tested, especially a database. Your unit test should test that the correct sql is being generated, not that the database is doing the right thing.

share|improve this answer
    
Well so there is a scenario where the function is searching for records. I am unit testing the function. the search function internally executes the query against the database. In order for me to not get an exception, I would need something which can execute the query the search function is trying to execute. I am definitely not trying to test the database part. –  dineshsbisht Dec 11 '13 at 22:21
    
Mockito or JMock will be your friend. They'll mock the everything you're not testing. My recommendation is Mockito, it's easier to work with I think. If you need more power to test, then add in PowerMock's PowerMockito lib. –  Jim Barrows Dec 12 '13 at 16:16

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.