Self-Reflection on Exception-Handling

I spent this week on refactoring my code of past three months. It’s a torturous work. And the one which makes me want to tear my hair out, is Exception-Handing. I luckily followed almost all the Not-To-Do listed in <Exception-Handling Antipatterns> .

Actually Exception-Handling design have great influence on total quality.Bad Exception-Handling sometime ruin good design. I list here some guideline mentioned in <Toward Exception-Handling Best Practices and Patterns> .Make it right even if it goes wrong.

• Don’t try to handle coding errors.
• Avoid declaring lots of exception classes.
• Name an exception after what went wrong, not who raised it.
• Recast lower-level exceptions to higher-level ones whenever you raise an abstraction level.
• Provide context along with an exception.
• Handle exceptions as close to the problem as you can.
• Assign exception-handling responsibilities to objects that can make decisions.
• Use exceptions only to signal emergencies.
• Don’t repeatedly rethrow the same exception.

JMeter

JMeter under Apache project is an application designed to load test C/S software.JMeter can be used to simulate a heavy load on a server , network or object to test its strength or to analyze overall performance under different load types.

 

After extracting JMeter on your computer, you can run it by jmeter.bat. To begin with JMeter, you need to build a test plan.A test plan describes a series of steps JMeter will execute when run. A complete test plan will consist of one or more Thread Groups, logic controllers, sample generating controllers, listeners, timers, assertions, and configuration elements.