Unit tests for one main method

Question

I have a method. What is the best practice to unit testing? You can make a mock Connection and ResultSet and pass as a method parameter as an object but I find it stupid, unprofessional solution.

public static void playA() { MyObject object = check("cat"); // some stuff... } private static MyObject check(String s) throws SQLException { // some stuff checking string MyObject o = methodA(s); // some stuff doing on the object return o; } private static MyObject methodA(String s) throws SQLException { Connection c = MySettings.getConnection(); PreparedStatement ps = c.prepareStatement("select * from Objects where type = ?"); ps.setString(1, s); ResultSet resultSet = ps.executeQuery(); while (resultSet.next()) { // mapping return object; } return null; }

Nicolas Fontenele · Accepted Answer · 2016-12-01 02:34:01Z

My take is that it should be according the level of abstraction you want to test. Mocking Connection and ResultSet can be fine if you want to check the the logic of your SQL for example.

If you want to be precise testing the database connection layer you can use tools for unit testing database like http://dbunit.sourceforge.net/

Also try to have your code as most Object Oriented as possible. that would help you in testing ( although I know it's probably just an example )

Collectives™ on Stack Overflow

Unit tests for one main method

1 Answer 1

Comments

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Related