Today I have downloaded for 150 MB of podcasts from software engineering radio and developer works websites ranging from the topics on software architecture, java, MDD etc.
This is a new start and hope to make use of my commute time with this.
http://www.se-radio.net
Also I came across a blog space where Tim Lee writes.
http://dig.csail.mit.edu/breadcrumbs/blog/4
Wednesday, June 18, 2008
New tools
As part of the development in the new SOA and MDD approach, I will have to use a set of tools new to me.
I will have to use a requirements management tool, business process modeling tool, and a workflow tool.
Let us see how this experience turns out. After a long time, I am up in a project with high learning curve. It is good to be part of it.
I will have to use a requirements management tool, business process modeling tool, and a workflow tool.
Let us see how this experience turns out. After a long time, I am up in a project with high learning curve. It is good to be part of it.
Monday, June 16, 2008
Unit testing improvements
Last year, I was maintaining the J2EE application I had developed. Hence there was not much new things to learn in terms of the technology. Hence we started focusing on the Unit testing.
We moved to Agitar framework to help in our unit testing crusade. We were using JUnits before.
Agitator is a powerful tool. It generates the Junit test cases from your code. Also it generates powerful test cases in its own propritary format. It reads the code and suggests assertions that it observes from running a unit of method. For the first time it generates the data for the unit. If it is not able to generate the data or if we need more precise data we can assist it by specifying the data range or type. We can do this by providing mock classes and factories. It is powerful on these fronts. Also one place where it helps very much is that it identifies any uncaught error scenarios like Nullpointer, ArrayIndexOutOfBounds, ClassCast exception etc.
The developer will have a learning curve initially. But once he believes it and appreciates it, the benefits are good. It forces you to write yur methods following good test driven proniciples. If you have not done it that way, you will have a hell of a time testing a single method.
It will be more easier to test three methods each of 20 line size than to test a single method of 60 line size. Although this is a basic software engineering concept that with the cyclomatic complexity being increased your test case complexity is increased exponentially, due to agitars coverage analysis, we can catch it real time in the dash board for managers if the method is not completely tested.
For more information on the tool refer www.agitar.com
We moved to Agitar framework to help in our unit testing crusade. We were using JUnits before.
Agitator is a powerful tool. It generates the Junit test cases from your code. Also it generates powerful test cases in its own propritary format. It reads the code and suggests assertions that it observes from running a unit of method. For the first time it generates the data for the unit. If it is not able to generate the data or if we need more precise data we can assist it by specifying the data range or type. We can do this by providing mock classes and factories. It is powerful on these fronts. Also one place where it helps very much is that it identifies any uncaught error scenarios like Nullpointer, ArrayIndexOutOfBounds, ClassCast exception etc.
The developer will have a learning curve initially. But once he believes it and appreciates it, the benefits are good. It forces you to write yur methods following good test driven proniciples. If you have not done it that way, you will have a hell of a time testing a single method.
It will be more easier to test three methods each of 20 line size than to test a single method of 60 line size. Although this is a basic software engineering concept that with the cyclomatic complexity being increased your test case complexity is increased exponentially, due to agitars coverage analysis, we can catch it real time in the dash board for managers if the method is not completely tested.
For more information on the tool refer www.agitar.com
Whats the latest news...
We just started some hard core Model Driven Development in our team.
I am not new to this space completely. We tried to emulate the concepts without using any good tools. Now we take the help of a framework and the necessary tools.
We will be using IBM Business driven development suite of tools.
Let us see how it goes.
I am not new to this space completely. We tried to emulate the concepts without using any good tools. Now we take the help of a framework and the necessary tools.
We will be using IBM Business driven development suite of tools.
Let us see how it goes.
Back after a long time
Back after a long time here.
I just read this.
Apache JMeter is a Java application designed to test server applications.
It can be used to:
* generate test loads
* test functional behaviour
* measure performance.
It includes support for protocols such as HTTP(S), JDBC, JMS, FTP, and others.
It can also be extended with user-written code.
I did not know that we can do functional testing using JMeter. I thought it to be a performance testing tool.
I just read this.
Apache JMeter is a Java application designed to test server applications.
It can be used to:
* generate test loads
* test functional behaviour
* measure performance.
It includes support for protocols such as HTTP(S), JDBC, JMS, FTP, and others.
It can also be extended with user-written code.
I did not know that we can do functional testing using JMeter. I thought it to be a performance testing tool.
Subscribe to:
Comments (Atom)