Quiz on Error Types in Programming

Which of the following is NOT a general category of error?

• Sneaky Error

• Syntax error

• Logical error

• Runtime exception

What general term to software engineers use to describe errors in programs?

• Flops

• Breakpoints

• Tracepoints

• Bugs

Which of the following is NOT displayed in a syntax error message?

• The file name where the error was found

• The suggested best practice for avoiding the error in the future

• The line of code where the error was found

• A carat (^) pointing at the likely location of the error within a statement

When you get a syntax error, what should you do if you can't find the problem at the line of code where the carat is pointing?

• Look backwards (upwards) at earlier statements to see where the problem starts

• Look downwards (forwards) at later statements to see where the problem ends

• Engage the debugger and set a breakpoint

• Call the Python support hotline

If a program runs without any error messages, but doesn't do what you want it to do, what kind of error do you likely have in your code?

• Logical error

• Syntax error

• Runtime exception

• Any of these is possible

When do you normally see the effects of a logical error?

• When the program is running

• Before the program starts

• After the program ends

• Any of these times is possible

What happens when a runtime exception is encountered?

• Your program continues to run but may not behave the way you wanted

• Your program hangs forever without any more input or output

• Your program halts completely with an error message

• An automatic error report is sent to the Python Software Foundation

Why are logical errors sometimes harder to find and fix?

• You do not see any error messages that give you hints about the problem

• The logical error messages are more complicated than other error messages

• You have to keep re-starting your program after it crashes

• You don't have any tools to help you find and fix those kinds of problems

When conducting a code review, in what order should you normally examine your statements?

• From top to bottom, in the order they normally execute

• From bottom to top, working backwards

• Start with the longest and most complex statements first

• Start with the shortest and easiest statements first

When Python runs a particular statement, which of the following will influence the behavior and success of that statement?

• Earlier statements that have already run to create or update variable values

• The comments you have left in the code for that statement

• The statements that will run afterwards to provide more information

• All of these are true