Agitator One vs RAD Component Testing

1) RAD misses the snap shot facility. This will be very useful when you look through the failed assertions.

2) Also the test stubs generated by RAD does not have all the boundary conditions provided by the agitator by default.

3) On agitation, Agitation reads the code and provides plain assertions based on boundary conditions and output. RAD generates only empty stubs left for the developer to fill.

4) Also the dashboard facility is something very good in Agitator one which is not provided in RAD component testing.

5) The UI of Agitator One is so intuitive where as with RAD it is not the case.

6) All the features of Agitator One are cohesive or located together while with RAD it appears scattered all over the UI.

7) With RAD the claim is that the test data can be associated with variables, method parameters etc. where as Agitator does not allow vairables. But still the effect is same because with agitator you work on your code andin your code, you define the boundary conditions / test data on the method parameters where as in RAD you work on the generated tests and in that the method of the code is just called. In that case the method parameter is declared as variable in the test. All RAD means is that you can associate test data with this variable which is nothing but equivalent to the Agitators method parameter test data association.

8) There is a perspective difference between RAD and Agitator One. Agitator One allows the developers to be on their code and define declarative tests on their code where as with RAD you have to work on the generated tests (nothing but Test Stubs) which is like a separate effort. Agitator clearly wins over in this point that the developer need not leave his code and still associate tests to it.