What is the best method to test db update in testNG?

Question

I'm trying to write a TestNG to test db update for a property.Pseudocode is as below.

@Parameters({"newValue"})
@Test
public void testUpdateValue(@Optional String newValue)
{
    String originalValue = getValueFromDataBase(); //get Original value
    updateValue(newValue);   //update property to newValue
    String updatedValue = getValueFromDataBase();    //get updated value from db
    Assert.assertEquals(updatedValue == newValue, true);   //test value updated correctly.
    updateValue(originalValue);     // reset to origal value after test
}

am I using the correct method to test the db update? or Any other solutions are there in testNG?

Thanks in advance.

score 0 · Answer 1 · answered May 06 '16 at 10:30

It looks some thing not good at assertion.

   Assert.assertEquals(actual, expected);

for assert equals you need to provide actual value from db and your expected value. If both are equal then it will pass else fail.

   Assert.assertEquals(updatedValue, newValue);

Thank You, Murali

score 0 · Answer 2 · edited May 23 '17 at 12:07

There are 3 problems I see with this test:

As mentioned by murali, you should do Assert.assertEquals(updatedValue, newValue). This ensures that your assertion errors are useful. If you do Assert.assertEquals(updatedValue == newValue, true), then your message is going to be "False is not equal to True", instead of "'Joe' is not equal to 'Bob'".
Your test depends on getValueFromDatabase() working correctly. If getValueFromDatabase() returns a random value each time, or the same value, or appends something, then this test will fail, even if updateValue() works.
If updateValue() doesn't work, then you are leaving your database in a dirty state.

To solve problems 2 and 3, I recommend Mocking your database. What this entails:

It looks like all of your database methods are static. This is a bad thing. Wrap your database in an object, and use object methods to hit your database.
Your Database object would ideally take parameters in its constructor that define which network it uses.
Create a mock object that represents a network (that you passed to your constructor above). It'll have the same methods as a normal network, but it won't actually send any requests.
Then, in your test, you can test to see if dataBase.updateValue() sends an UPDATE across the network.

More info on mocking

What is the best method to test db update in testNG?

2 Answers2