I hacked together a solution for this. I’m not sure if there’s a nicer way to do it. Feel free to fix it up...
After my last commit, we are down to 20 ignored tests total. It would be great if someone could check the one test that’s failing on the CI server. It’s passing on my machine, so I’m not sure what’s wrong there. If there’s no easy way to fix that test, we can set it to ignore again, but it looks like a good test to have. On Dec 31, 2014, at 11:22 PM, Harbs <harbs.li...@gmail.com> wrote: > Piotr, I have a question: > > I’m looking at the EventOverrideTest. > > The old tests look like they were run via xml like this: > <TestCase functionName="keyDownDerivedTest"> > <TestData name="overrideEditManager">true</TestData> > <TestData name="flash">false</TestData> > <TestData name="fileName">empty.xml</TestData> > <TestData name="tb_rtl">false</TestData> > <TestData name="rl_ltr">false</TestData> > </TestCase> > > These values were different for the different test cases. > > How is TestData.overrideEditManager supposed to be set on a case-by-case > basis in the current setup? > > There’s also a variable called TestData.eventOverride. I’m not sure how > that;’s supposed to be set. > > On Dec 31, 2014, at 12:36 AM, piotrz <piotrzarzyck...@gmail.com> wrote: > >> Harbs, >> >> Congratulations! You are absolutly the best! :) >> >> Do you still want me to look into tests ordering? >> >> Piotr >> >> >> >> ----- >> Apache Flex PMC >> piotrzarzyck...@gmail.com >> -- >> View this message in context: >> http://apache-flex-development.2333347.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p44017.html >> Sent from the Apache Flex Development mailing list archive at Nabble.com. >
