Home/ Questions/Q 4255704
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-21T05:15:17+00:00

So, here’s the deal. I’m currently working in a Ruby on Rails environment and

  • 0

So, here’s the deal. I’m currently working in a Ruby on Rails environment and have been for ~1 year now. Before that I was in C++/Java land for almost a decade. I’m (still) trying to figure out what the Ruby way is when it comes to asserts.

I’m not worried about the technical detail. I know TestUnit has asserts which can be used in the testing environment and I know I can add my own assert methods to my Ruby project and use them in production Rails to lock down known conditions. The question is: What is the Ruby way for ensuring something in code that I know should/not happen?

For the record, I’ve been asserting in tests and raising in production. I still can’t help but miss my production asserts…

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Asserts really shouldn’t be used in production code for two reasons.

    1. assert x is very functional, and as such hard to read. Using a raise/if combo adds readability.

    2. assert doesn’t make it clear what error will be raised if the condition fails. While,

      raise ObscureButInformitiveError if condition

      lets the application layers further up do something relveant. Such as emailing an admin, or writing to a perticular log.

    • 0