The setup is where you create any objects that you need to create. This is the test name, plus a way to group together all the components of the test itself. Then you need to create a describe block to group all your tests together & to tell RSpec which class you are testing. This is the initial code for writing your first RSpec test. We are going to write a simple application that finds factorial numbers. To understand how RSpec works let’s go over an example step-by-step. Most job applications will appreciate your testing skills, increasing your chances of landing the job. Tests can help you uncover corner cases & document them. If you are writing some complex logic, then you want to make sure it’s working with many different inputs & not just with one example you came up with. It helps you make sure your code is producing the results you expect When you are doing TDD you get a feedback loop that tells you what to focus on next, useful if you get distracted easily. Your tests describe what your application should be doing. …having tests increases your confidence! It helps document your code If you don’t have a test suite then you don’t want to touch your code, because of the fear of something breaking… Here’s why: It builds a safety net against errors (especially useful for refactoring) 6 How to Run Code Before All Your Tests.1.0.4 It helps you make sure your code is producing the results you expect.1.0.1 It builds a safety net against errors (especially useful for refactoring).

Rspec allow raise error