[Neos] [RFC] Disable Interface related Behat tests
rens.admiraal at typo3.org
Sun May 19 20:13:38 CEST 2013
I feel like Christian, but disabling the tests would be a bad thing. I
do think it's a nice chance to get familiar with behat, we'll have to
fix a lot of tests the next weeks :)
Op 5/19/13 11:44 , Christian Müller schreef:
> That would be awesome!
> I just saw that we get constantly failing tests during the UI
> refactoring. But of course it would make more sense to keep the tests
> running meanwhile.
> Obviously some change was merged without waiting for he CI job so that
> the failing Behat tests were not detected...
> On 19.05.13 11:19, Berit Hlubek wrote:
>> I just talked about it with Christopher and the tests should not be deactivated, because failing is exactly what they are supposed to do if stuff doesn't belong together any more.
>> The goal should be that everyone is able to fix the tests after stuff changed. For this moment Christopher and me will do the fixing today if Sebastian didn't already do it and I think Christopher will also write a short guide so that everyone will be able to get the tests running again if some changes got in.
>> Am 18.05.2013 um 17:47 schrieb Christian Müller:
>>> Hi all,
>>> as nice as I find the new Behat tests currently they seem to fail due to
>>> the beginning of the UI reworkings and as more of that is coming I would
>>> like to disable all Behat tests that are UI related and just keep
>>> minimal tests like if the login works. Then we can rework and add to the
>>> tests as soon as the UI is fairly stable.
>>> If you are OK with that could someone involved in setting that up
>>> disable them as I have no idea how to do so.
>>> Neos mailing list
>>> Neos at lists.typo3.org
More information about the Neos