I think the confusion over two different test methods has reached a
high level and Dave and I agreed previously that we should try to make
the API driven version the default during this release cycle - but it
is not our call :).
Greg - is there anything else you feel that needs to happen to at
John, Peter,
The buildbot builders are already using the api interactor for both
functional tests and the install and test framework.
--Dave B.
On Fri 18 Jul 2014 11:34:01 AM EDT, John Chilton wrote:
I think the confusion over two different test methods has reached a
high level and Dave
On Fri, Jul 18, 2014 at 5:14 PM, Dave Bouvier d...@bx.psu.edu wrote:
John, Peter,
The buildbot builders are already using the api interactor for both
functional tests and the install and test framework.
--Dave B.
Great news.
When did that happen? Did it cause any regressions (and
can/did
Thanks Peter, I guess I should then rely on API based tests.
On 15 July 2014 14:18, Peter Cock p.j.a.c...@googlemail.com wrote:
Hi Saket,
From memory the Twill tests are fragile with the output file order in the
XML.
John was discussing switching the default from the Twill to API backend,
On Wed, Jul 16, 2014 at 7:44 PM, Saket Choudhary sake...@gmail.com wrote:
Thanks Peter, I guess I should then rely on API based tests.
If it is just the order, make sure the order of the output files in the test
is consistent with that in the outputs and it make be OK with Twill...
I wonder if
Hi Saket,
From memory the Twill tests are fragile with the output file order in the XML.
John was discussing switching the default from the Twill to API backend,
not sure when that is happening though...
Peter
On Tue, Jul 15, 2014 at 9:31 AM, Saket Choudhary sake...@gmail.com wrote:
I
