Should you Unit Test business logic methods consist mainly of a query?

Question

I have a business logic level with a wide range of classes and their corresponding methods. Creating a Unit Test for a method is usually given, but in some cases the method really just returns a set of matching records from the database. It seems silly to write Unit Test, for example, to store five matching records, and then call the BLL method and see if it will return all five records.

What is the best thing here? What are you actually doing - unlike what you would like to say, what are you ideally doing?

Answer 1

, : - , , , -?

, - , .

Unit Test . :

• - ( ), , . Unit Test , , , .

• - (, , -), .

• , - , , . , ... .

Answer 2

DBUnit, , , . , . , , , .