what is an example of too much test cases?

Sahil Grover — Wed, 05 Feb 2020 16:28:50 +0000

Sometimes I wonder that I am writing too many test cases which test the exact same thing. Assuming there is a class

class KlassA
  def do_something
    b = KlassB.new
    b.do_something_more
  end

  def do_something_else
    c = KlassC.new
    c.do_some_other_thing
  end
end

Now, if I have written test cases for KlassB, do_something_more and KlassC, do_some_other_thing. Should I write test cases for KlassA, do_something and KlassA, do_something_else ? Should I even write test for KlassA at all.

Why or Why not ?

Use DIG save headache

Sahil Grover — Mon, 03 Feb 2020 18:00:52 +0000

Lets assume we send a request and get the following response as JSON

user = {
  user: {
    address: {
      street: '123 Some street'
    }
  }
}

Now in order to get the street address, the simplest way would be street = user[:user][:address][:street] but what if address is empty or even the user object is empty.

In order to avoid the error sometimes we end up writing code which looks like

if user[:user] && user[:user][:address] && user[:user][:address][:street]
 street = user[:user][:address][:street]
end

The above code is valid, but looks quite ugly. With ruby a less known functionality is hash.dig. As mentioned in ruby docs dig Retrieves the value object corresponding to the each key objects repeatedly.

So, if we use dig in the above example it becomes

 street = user.dig(:user, :address, :street) || 'Default Street'

Cheers

DEV Community: Sahil Grover

what is an example of too much test cases?

Use DIG save headache