Repository files navigation

In this lab, you'll be reading error messages from tests. This lab is designed so that both running the filesand running the test suite via thelearn command will show the error messages for you to decode. Moving forward though, you'll be reading error messages mainly through running the test suite.

Get started by opening this lab with by pressing the Open button on the toolbar so you can follow along with the video and solve this lab.

1. Read the three different parts of an error message.
2. Identify four error types- name errors, syntax errors, type errors, and division errors- and fix them
3. Describe a test suite, where it's found in a lab, and its purpose
4. Use thelearn command in terminal to run the tests for a lab.

Download MP4

Error messages have 3 parts:

lib/a_name_error.rb:3:in `<main>': undefined local variable or method `hello_world' for main:Object (NameError)

1. The location of the error, the "where".

lib/a_name_error.rb:3:in `<main>':

• lib/a_name_error.rb is the file the error occurred in.
• 3 is the line of code with the error.
• <main> is the scope of the error.

2. The description, the "why".

undefined local variable or method `hello_world' for main:Object

The interpreter does the best job it can to tell you what it thinks went wrong.

3. The type of error, the "who".

(NameError)

This is aRuby Error Type.

You've solved games ofClue with less information. This is one of the best parts of programming: debugging and fixing errors. It's like you're a detective solving a crime. The only bad thing is that more often than not, you're also the criminal that caused the error in the first place.

Errors are clues, and reading them is the interpreter telling you what to do to fix the program and move on.

NameErrors are caused when a given name is invalid or undefined. Whenever the Ruby interpreter encounters a word it doesn't recognize, it assumes that word is the name of a variable or a method. If that word was never defined as either a variable or a method, it will result in a name error.

Syntax errors are pretty self-explanatory: they're the result of incorrect syntax. Thankfully, they're usually followed by a guess about the location of the error. For instance:

2.timesdoputs"hi"

Will result in:

2: syntax error, unexpected end-of-input, expecting keyword_end

Here, Ruby is saying that on line 2, there is a missingend (everydo keyword must be followed by some code and then anend keyword). Always read the full details of syntax errors and look for line numbers, which usually appear at the beginning of the error message.

When you try and do a mathematical operation on two objects of a different type, you will receive a TypeError. For example if you try and add a string to an integer, Ruby will complain.

1 +"1"

Will produce the following error:

TypeError: String can't be coerced into Fixnum

DivisionErrors are caused when a given number is divided by 0.

The tests for each lab will be found inside thespec directory of that lab. Tests are programs, written using the RSpec testing library, that are written to make sure your program is running properly. Generally, tests will call on the methods you define in your programs and check to see if they are working the way they are expected to.

In the future, you will learn how to read tests more thoroughly and even how to write your own tests. For now, all you need to understand is that the code in thespec directory is there to test the code in your program. When you run thelearn or therspec command in your terminal in the directory of the lab you are working on, that runs the code in yourspec file and tests your program. The output that appears in your terminal is the result of running those tests. If you pass a test, the output will generally appear green, otherwise, it will appear red and be accompanied by the types of error messages that we're discussing in this README. Paying attention to those error messages will help you to pass the test.

STOP. If you haven't watched the above video, you are making life much harder for yourself! Watch the video lecture above before attempting this lab. : )

Did you watch it? Okay, great. Let's proceed. The point of this lab is to get you comfortable reading error messages and fixing simple programs.

1. Open this lab.

2. Runlearn from the root of the lab's directory. You should see a lot of red — this is okay! Tests have failed, and now we can fix them.

• Read the errors. Scroll through the entire output to get a sense of what the failures are trying to tell you. What doesexpected no Exception, got #<NameError: undefined local variable or method `hello_world' for main:Object> with backtrace mean? How can we fix it?

• Each error prints out astack trace, which points to where the code failed and attempts to follow itup the stack — that is, through the bits of code that ran leading up to the failure. You can use these stack traces to pinpoint which line(s) of code need your attention.

• These stack traces can also point you to which files you should run to get a better sense of the errors. Which leads us to step 3:

3. Run each of the files in thelib directory using theruby command.

• From the lab directory, try:ruby lib/a_division_by_zero_error.rb to run that program. You should get output about an error in the program. Read the error message and open that file in your text editor and see if you can fix the error. When the error is fixed and you run the file viaruby, you'll simply see no output at all, no errors or anything. Confirm this by running thelearn command and seeing that you have a passing test and 3 remaining failures. For example, if you see aZeroDivisionError, you'll have to figure outwhere Ruby is trying to divide by 0 and change the code so that the division operation is valid (i.e., something other than 0).

• Run each file viaruby lib/<file name>, fix the errors, and confirm withlearn. Then follow the next error's stack trace back to the next failing file inlib/ and repeat the fixing process until you're done and all the tests pass. Pay attention to the filenames inlib if you need hints for what kind of error to look for.

4. Once your code is passing with thelearn command, submit the lab withlearn submit

Feel proud. Being able to read an error message and fix it, no matter how basic, is a huge step in being a programmer. Get comfortable with broken code. It's totally normal in programming.

ViewIntro to Reading Ruby Error Messages on Learn.co and start learning to code for free.

ViewReading Error Messages on Learn.co and start learning to code for free.