I if you have read the FAQ's for QAForums, you would know that the first thing to try is a search for what you seek. In the upper right-hand corner of this screen is a search engine for the site. Click "ADVANCED" and search on "EXCEPTION HANDLING" in the "AUTOMATED TESTING" form. There are 10 or twelve references there. Also search on "EXCEPTION" & "EXCEPTION". Then search the other forums also. Let us know if there is no information to help you, but please put some context into your question. It's hard enough to read minds, but even more difficult from long distance!
Success is the ability to go from one failure to another with no loss of enthusiasm.
~ Winston Churchill ~
Exceptions by definition are events that are not what we expected to see. You just had 3 exception responses, each taking a different path from what you had expected. In a test case context you can simply direct each of these paths to some common "test failed" exit and record that fact, or specific exceptions could trigger a different set of test continuation actions that recover the flow of work into a different alternative path in which you do some different processing. Primitive scripts simply expect you to enter data in some field and then to observe the response, true or false. Complex scripts will trigger further data entry depending on the response contents, which can be a valid option or some error status that may require a special intervention, so not all of the cases that have alternate responses are by definition exception paths.