I'd like to propose we consolidate the integration tests into a single
project. The major driver of this is that as the tests get more complex
it's hard to split the step definitions across the current boundaries  For
example, to test RAVE-845, you need to create a user, log in as them,
friend someone, logout, login as an admin, and try to delete the user. Most
of those steps exist, but they are in at least two different projects. This
would require duplicating a bunch of steps across multiple projects which
would add to long term maintenance.

Even with consolidating into a single project, we can still organize the
stories themselves inside that project to make them easier to
find/understand. It would simplify things and maximize reuse without
negatively impacting flexibility. The only potential impact is that it
might run all the tests under a single web driver instance which would keep
cookies but I think that can be easily managed.

Please let me know if there are any objections or major factors I'm not
considering. If not I'll work on this over the next couple days.

Thanks,
Chris

Reply via email to