Selenium tests in separate repo or together with application code?

[KenCK]

We currently have a separate repo for our Selenium tests (in Java).
Wondering if this is the norm or if there are benefits to keeping the
tests in the same repo as the application code?

If you are coupling the tests with the code, do you keep the tests
segregated in a separate folder or do you keep them together with
various routes/directories?

Appreciate any feedback. Thanks!

[Ross Patterson]

We have several Subversion repos, for a variety of reasons, not all of which I agree with. We keep our tests in the same repo as the front-end code (C#, ASP, ASP.NET, JavaScript), on the assumption that most changes that affect tests are in that same repo. We started doing that because it allowed us to commit one changeset that contained both product-changes and test-changes caused by them, but we quickly found that the more common practice is to commit them separately, and for the test changes to lag (i.e., we sometimes see tests break and then fix them afterwards). Our mainstream code is in /trunk/src/main, and the test in /trunk/src/test, but that's just a convenience, and very little of our build system knows or cares about that.

Ross

[Dave Justin]

Generally, putting the tests in the same repo as your code base is a
good idea. Keep in mind that you probably don't want the tests in
your web root if you can help it -- it should go in a sibling
directory to your source code.

/myproject
/source
/tests

The main benefit of putting it in the same repo, in a sibling
directory, is that the code and the tests get versioned together.
This way, you never have to wonder which revision of your test
repository corresponds to which revision of your source code. That
also allows you to set up a Continuous Integration server to run your
tests automatically, if you wanted to do that. Also, if you branch
your source code, the tests will get branched along with it -- you
almost always want that.

Just my two cents. Hope that helps!

[Paul Grandjean]

On my last project we put our tests within the same repository as the project.  It worked well for us, simply to have a one-stop place for all the code, test and otherwise, in one place central for the whole team.

To avoid not-yet-ready-tests breaking the build we used cmd-line optinos passed to maven to control whether we skipped tests or not.  

Paul

--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To post to this group, send email to seleniu...@googlegroups.com.
To unsubscribe from this group, send email to selenium-user...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/selenium-users?hl=en.

[KenCK]

Thanks for the replies everyone!

[Tarun Bhadauria]

I had posted a similar question in SQA forum some time ago, you might find it interesting -

http://sqa.stackexchange.com/questions/2143/keeping-automation-code-away-from-application-source-code/

[KenCK]

Thanks Tarun, some good points there to consider.

On Jan 19, 9:09 pm, Tarun Bhadauria <tkum...@gmail.com> wrote:
> I had posted a similar question in SQA forum some time ago, you might find
> it interesting -
>

> http://sqa.stackexchange.com/questions/2143/keeping-automation-code-a...