Hi Cristian,
I don't thing there is a necessity for integration testing, but we
definitely need to unit and integration test. Other tests we should
also include would probably include load tests so we can have some
data for capacity planning.
I am not familiar with
http://jbehave.org/, but I will definitely
check it. Thank you for the link. However, the main thing is to keep
things simple and flexible. We could also test our user stories
directly in the unit tests.
I agree about Junit and Easymock. Junit 4.7 library depency is already
in the pom file. You can add Easymock.
I am a little familiar with dbunit; but I am not familiar with
http://www.dbmaintain.org/. I will check that too.
All in all I have no preference for any testing framework. The main
point is to get things tested in a way we can be confident that our
tests are sensible (breath and scope is adequate). As long as we don't
spend more time setting up test infrastructure than writing actual,
usable code. We have to strike a good signal vs noise ratio. For the
database, you can test everything you need to give you confidence that
the DAO is working as it should. So choose whatever tool you think is
best.
For me, the UI testing involves inspection of the DOM resulting from
the GWT code, that the visual part; i.e making sure the UI looks as
the intended (the CSS is corretly applied) and making sure that the
ApplicationController calls the right URI for the right widget, with
the right header params.
I am setting a local Hudson continuous Build server on my machine. I
am looking for a service on the cloud that we can use. That way we can
both see what is happening. I will let you know as soon as I find a
suitable host.
Richard
On Jan 18, 1:32 pm, colaru <
col...@gmail.com> wrote:
> Hi Richard.
>
> I understand that you prefer to make unit/integration testing. We must
> talk about how we want to do the testing.
>
> As I know we can have this types of tests:
>
> - acceptance testing (maybe using BDD with a framework likehttp://
jbehave.org/
> (runnable stories) - nice to have this - will keep the spec clean)
> this can be done by you from interface without calling the code
> - integration testing (at the services layer for me) - and also in the
> presentation layer for you if you want; for DAO I think is unit
> testing and not integration because we cannot think at DAO without
> database.
> - unit testing (at services level mocking DAO's for me) - Also at the
> presentation level for you (mocking in GWT the services); at the DAO
> level for me
>
> So for me I need:
>
> In general: JUnit 4
> For DAO:
http://www.dbmaintain.org/overview.htmlorhttp://www.dbunit.org/