Mozilla

NAVIGATION
CATEGORIES
REFERRENCE
LINKS
  • Where to put automated tests and testing tools

    0 answers - 1198 bytes - related search similar search Add To My Delicious Add To My Stumble Upon Add To My Google Mark Add To My Facebook Add To My Digg Add To My Reddit

    I think we have enough stuff (test cases, test tools, aux files) to
    warrant placing it in source control. Somewhere.
    QA and dev folks need to put stuff in. QA, dev, and tinderboxes need to
    check stuff out.
    I think we could use either the main cvs repository, or the private mofo
    one.
    Using the main cvs repository is good in that everyone can access it,
    but bad in that not all folks we might want to grant check-in privs for
    tests are folks we want to grant access to the entire repository.
    Using the mofo repository is good in that the tinderbox configs and
    release scripts live there, but bad in that it might be a pain to have
    tests and code in separate repositories.
    I suggest we use subdirectories of mozilla/tools/test-harness (already
    exists) for test tools such as the visual regression test extension, put
    test cases in a ./test subdirectory where the code under test lives, and
    put suites (lists of test cases) in mozilla/tools/test-suites.
    I also suggest creating a cvs module (or some other mechanism) for
    checking out just the tests and packaging them up for "installation"
    somewhere else.
    Thoughts?

Re: Where to put automated tests and testing tools


max 4000 letters.
Your nickname that display:
In order to stop the spam: 1 + 0 =
QUESTION ON "Mozilla"

EMSDN.COM