On Feb 13, 2006, at 9:49 PM, Mike Taylor wrote:


On Feb 13, 2006, at 11:33 PM, Mikeal Rogers wrote:

Grant had a suggestion today that it may be nice to have an option that restarted chandler and cleared the repository in between tests, so each test in a suite ran in a clean state.

Currently, IIRC, the functional test suite is run with the --create parameter first to establish an empty repository.

Just to make sure we are on the same page.

I know that we run this at the beginning of the suitea single test which is run by do_test.

The suggestion Grant had that I was proposing was that when an entire suite is run having the option of stoping and restarting chandler with a fresh repository in between each test in the suite. Sorry if that wasn't clear.

Also, I'm suggesting this as an _option_, not the default run process for a functional suite. There is more value, in my opinion, in running the entire suite on the same repository in the same chandler instance, but I think this option could help for debugging.


I think we (QA, myself and anyone interested) need to sit down and walk thru our current testing setups to 1) audit the recent changes to make sure they are all valid/functional and 2) to have a code review so we are all on the same page

+1


:)


---
Bear

Build and Release Engineer
Open Source Applications Foundation (OSAF)
[EMAIL PROTECTED]
http://www.osafoundation.org

[EMAIL PROTECTED]
http://code-bear.com

PGP Fingerprint = 9996 719F 973D B11B E111  D770 9331 E822 40B3 CD29


_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev

Reply via email to