You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Christofer Dutz <ch...@c-ware.de> on 2015/03/30 13:22:18 UTC
[LAST CALL] FlexUnit 4.3
Hi,
I am preparing to start a new release of FlexUnit. Even if only a hand-full of bugs were fixed, this time I am intending on also releasing the Maven artifacts for FlexUnit so I think it's worth a 4.3 :-)
Eventually (depending on the german wether during the Easter public holidays) I'm planning on staging the RC next Monday. So if you have anything to go into the package ... get started right away :-)
Chris
Re: AW: [LAST CALL] FlexUnit 4.3
Posted by Alex Harui <ah...@adobe.com>.
We just want to see the source package before you start a vote on it.
Thanks
Alex
Sent from my LG G3, an AT&T 4G LTE smartphone
------ Original message------
From: Christofer Dutz
Date: Thu, Apr 2, 2015 12:46 AM
To: dev@flex.apache.org;
Subject:AW: [LAST CALL] FlexUnit 4.3
The staging repo is for the playing around ... the source package is needed for the release. I didn't quite see the point in deploying the source package to the Nexus as the source package is released otherwise.
Chris
________________________________________
Von: Justin Mclean <ju...@classsoftware.com>
Gesendet: Donnerstag, 2. April 2015 00:22
An: dev@flex.apache.org
Betreff: Re: [LAST CALL] FlexUnit 4.3
Hi,
> Ok so I staged the Maven output at https://repository.apache.org/content/repositories/orgapacheflex-1010/
Is there a source package there? I couldn't find one to review.
Thanks,
Justin
AW: AW: AW: [LAST CALL] FlexUnit 4.3
Posted by Christofer Dutz <ch...@c-ware.de>.
But eventually this would be worth solving first ... it seems the automatiacly generated runner generates code, which is not backward compatible. Eventually we could fix this, but I guess someone else could give this a look ... I'm more the tooling guy ;-)
Chris
________________________________________
Von: Christofer Dutz <ch...@c-ware.de>
Gesendet: Donnerstag, 2. April 2015 13:11
An: dev@flex.apache.org
Betreff: AW: AW: AW: [LAST CALL] FlexUnit 4.3
There were different compilations of FlexUnit available in the earlier days ... perhaps to avoid that error?
Chris
________________________________________
Von: Frédéric THOMAS <we...@hotmail.com>
Gesendet: Donnerstag, 2. April 2015 13:05
An: dev@flex.apache.org
Betreff: RE: AW: AW: [LAST CALL] FlexUnit 4.3
Btw, now I'm thinking a little bit more about it, I think I used FU 4.1 with my last 4.6 project because of the same issue and used the 4.2 for apache SDKs.
Frédéric THOMAS
> From: webdoublefx@hotmail.com
> To: dev@flex.apache.org
> Subject: RE: AW: AW: [LAST CALL] FlexUnit 4.3
> Date: Thu, 2 Apr 2015 11:38:38 +0100
>
> Hi Chris,
>
> Yes, with the 4.6 but was pretty sure to remember that I used the FU 4.2 with my last 4.6 project (maven) and worked fine, maybe I've got a bad memory.
>
> > Did we change anything signifficantly?
>
> I'm not sure but that's pity if it means it won't work with the 4.6
>
> Frédéric THOMAS
>
> > From: christofer.dutz@c-ware.de
> > To: dev@flex.apache.org
> > Subject: AW: AW: [LAST CALL] FlexUnit 4.3
> > Date: Thu, 2 Apr 2015 10:18:19 +0000
> >
> >
> > Hi Frederic,
> >
> > well I think FlexUnit is compiled with Flex 4.12 (At least I think this is what I could see in the Ant scripts) ... in the End I think it will use whatever is located in the FLEX_HOME variable (Which is a 4.13 for the system I built the artifacts from). Judging from your message I would assume you let it run with 4.6, am I correct? Did we change anything signifficantly?
> >
> > Chris
> >
> >
> >
> > ________________________________________
> > Von: Frédéric THOMAS <we...@hotmail.com>
> > Gesendet: Donnerstag, 2. April 2015 10:53
> > An: dev@flex.apache.org
> > Betreff: RE: AW: [LAST CALL] FlexUnit 4.3
> >
> > Hi,
> >
> > Except the site [1] was extremely slow at me this morning at 9 am GMT +0, I've been able to run all my tests with this new FU version from IntelliJ.
> >
> > Out of the IDE, my build system for this app is done with Rake (ruby) and use a Runner app which once compile is launched by ADL, for this one, I had:
> >
> > VerifyError: Error #1053: Illegal override of generateMXMLInstances in mx.containers.ViewStack.
> >
> > at flash.display::MovieClip/nextFrame()
> > at mx.managers::SystemManager/deferredNextFrame()[E:\dev\4.y\frameworks\projects\framework\src\mx\managers\SystemManager.as:278]
> > at mx.managers::SystemManager/preloader_preloaderDocFrameReadyHandler()[E:\dev\4.y\frameworks\projects\framework\src\mx\managers\SystemManager.as:2627]
> > at flash.events::EventDispatcher/dispatchEventFunction()
> > at flash.events::EventDispatcher/dispatchEvent()
> > at mx.preloaders::Preloader/timerHandler()[E:\dev\4.y\frameworks\projects\framework\src\mx\preloaders\Preloader.as:515]
> > at flash.utils::Timer/_timerDispatch()
> > at flash.utils::Timer/tick()
> >
> > after running 4.6.0.23201/bin/adl bin/test/DesktopRunner-app.xml
> >
> > I've already seen this error somewhere but I forgot where though, did I miss something ?
> >
> > Note: I didn't test with flexcover.
> >
> > Thanks,
> > Frédéric THOMAS
> >
> > [1] https://repository.apache.org/content/repositories/orgapacheflex-1010/
> >
> > > From: christofer.dutz@c-ware.de
> > > To: dev@flex.apache.org
> > > Subject: AW: [LAST CALL] FlexUnit 4.3
> > > Date: Thu, 2 Apr 2015 07:45:22 +0000
> > >
> > > The staging repo is for the playing around ... the source package is needed for the release. I didn't quite see the point in deploying the source package to the Nexus as the source package is released otherwise.
> > >
> > > Chris
> > >
> > > ________________________________________
> > > Von: Justin Mclean <ju...@classsoftware.com>
> > > Gesendet: Donnerstag, 2. April 2015 00:22
> > > An: dev@flex.apache.org
> > > Betreff: Re: [LAST CALL] FlexUnit 4.3
> > >
> > > Hi,
> > >
> > > > Ok so I staged the Maven output at https://repository.apache.org/content/repositories/orgapacheflex-1010/
> > >
> > > Is there a source package there? I couldn't find one to review.
> > >
> > > Thanks,
> > > Justin
> >
>
AW: AW: AW: [LAST CALL] FlexUnit 4.3
Posted by Christofer Dutz <ch...@c-ware.de>.
There were different compilations of FlexUnit available in the earlier days ... perhaps to avoid that error?
Chris
________________________________________
Von: Frédéric THOMAS <we...@hotmail.com>
Gesendet: Donnerstag, 2. April 2015 13:05
An: dev@flex.apache.org
Betreff: RE: AW: AW: [LAST CALL] FlexUnit 4.3
Btw, now I'm thinking a little bit more about it, I think I used FU 4.1 with my last 4.6 project because of the same issue and used the 4.2 for apache SDKs.
Frédéric THOMAS
> From: webdoublefx@hotmail.com
> To: dev@flex.apache.org
> Subject: RE: AW: AW: [LAST CALL] FlexUnit 4.3
> Date: Thu, 2 Apr 2015 11:38:38 +0100
>
> Hi Chris,
>
> Yes, with the 4.6 but was pretty sure to remember that I used the FU 4.2 with my last 4.6 project (maven) and worked fine, maybe I've got a bad memory.
>
> > Did we change anything signifficantly?
>
> I'm not sure but that's pity if it means it won't work with the 4.6
>
> Frédéric THOMAS
>
> > From: christofer.dutz@c-ware.de
> > To: dev@flex.apache.org
> > Subject: AW: AW: [LAST CALL] FlexUnit 4.3
> > Date: Thu, 2 Apr 2015 10:18:19 +0000
> >
> >
> > Hi Frederic,
> >
> > well I think FlexUnit is compiled with Flex 4.12 (At least I think this is what I could see in the Ant scripts) ... in the End I think it will use whatever is located in the FLEX_HOME variable (Which is a 4.13 for the system I built the artifacts from). Judging from your message I would assume you let it run with 4.6, am I correct? Did we change anything signifficantly?
> >
> > Chris
> >
> >
> >
> > ________________________________________
> > Von: Frédéric THOMAS <we...@hotmail.com>
> > Gesendet: Donnerstag, 2. April 2015 10:53
> > An: dev@flex.apache.org
> > Betreff: RE: AW: [LAST CALL] FlexUnit 4.3
> >
> > Hi,
> >
> > Except the site [1] was extremely slow at me this morning at 9 am GMT +0, I've been able to run all my tests with this new FU version from IntelliJ.
> >
> > Out of the IDE, my build system for this app is done with Rake (ruby) and use a Runner app which once compile is launched by ADL, for this one, I had:
> >
> > VerifyError: Error #1053: Illegal override of generateMXMLInstances in mx.containers.ViewStack.
> >
> > at flash.display::MovieClip/nextFrame()
> > at mx.managers::SystemManager/deferredNextFrame()[E:\dev\4.y\frameworks\projects\framework\src\mx\managers\SystemManager.as:278]
> > at mx.managers::SystemManager/preloader_preloaderDocFrameReadyHandler()[E:\dev\4.y\frameworks\projects\framework\src\mx\managers\SystemManager.as:2627]
> > at flash.events::EventDispatcher/dispatchEventFunction()
> > at flash.events::EventDispatcher/dispatchEvent()
> > at mx.preloaders::Preloader/timerHandler()[E:\dev\4.y\frameworks\projects\framework\src\mx\preloaders\Preloader.as:515]
> > at flash.utils::Timer/_timerDispatch()
> > at flash.utils::Timer/tick()
> >
> > after running 4.6.0.23201/bin/adl bin/test/DesktopRunner-app.xml
> >
> > I've already seen this error somewhere but I forgot where though, did I miss something ?
> >
> > Note: I didn't test with flexcover.
> >
> > Thanks,
> > Frédéric THOMAS
> >
> > [1] https://repository.apache.org/content/repositories/orgapacheflex-1010/
> >
> > > From: christofer.dutz@c-ware.de
> > > To: dev@flex.apache.org
> > > Subject: AW: [LAST CALL] FlexUnit 4.3
> > > Date: Thu, 2 Apr 2015 07:45:22 +0000
> > >
> > > The staging repo is for the playing around ... the source package is needed for the release. I didn't quite see the point in deploying the source package to the Nexus as the source package is released otherwise.
> > >
> > > Chris
> > >
> > > ________________________________________
> > > Von: Justin Mclean <ju...@classsoftware.com>
> > > Gesendet: Donnerstag, 2. April 2015 00:22
> > > An: dev@flex.apache.org
> > > Betreff: Re: [LAST CALL] FlexUnit 4.3
> > >
> > > Hi,
> > >
> > > > Ok so I staged the Maven output at https://repository.apache.org/content/repositories/orgapacheflex-1010/
> > >
> > > Is there a source package there? I couldn't find one to review.
> > >
> > > Thanks,
> > > Justin
> >
>
RE: AW: AW: [LAST CALL] FlexUnit 4.3
Posted by Frédéric THOMAS <we...@hotmail.com>.
Btw, now I'm thinking a little bit more about it, I think I used FU 4.1 with my last 4.6 project because of the same issue and used the 4.2 for apache SDKs.
Frédéric THOMAS
> From: webdoublefx@hotmail.com
> To: dev@flex.apache.org
> Subject: RE: AW: AW: [LAST CALL] FlexUnit 4.3
> Date: Thu, 2 Apr 2015 11:38:38 +0100
>
> Hi Chris,
>
> Yes, with the 4.6 but was pretty sure to remember that I used the FU 4.2 with my last 4.6 project (maven) and worked fine, maybe I've got a bad memory.
>
> > Did we change anything signifficantly?
>
> I'm not sure but that's pity if it means it won't work with the 4.6
>
> Frédéric THOMAS
>
> > From: christofer.dutz@c-ware.de
> > To: dev@flex.apache.org
> > Subject: AW: AW: [LAST CALL] FlexUnit 4.3
> > Date: Thu, 2 Apr 2015 10:18:19 +0000
> >
> >
> > Hi Frederic,
> >
> > well I think FlexUnit is compiled with Flex 4.12 (At least I think this is what I could see in the Ant scripts) ... in the End I think it will use whatever is located in the FLEX_HOME variable (Which is a 4.13 for the system I built the artifacts from). Judging from your message I would assume you let it run with 4.6, am I correct? Did we change anything signifficantly?
> >
> > Chris
> >
> >
> >
> > ________________________________________
> > Von: Frédéric THOMAS <we...@hotmail.com>
> > Gesendet: Donnerstag, 2. April 2015 10:53
> > An: dev@flex.apache.org
> > Betreff: RE: AW: [LAST CALL] FlexUnit 4.3
> >
> > Hi,
> >
> > Except the site [1] was extremely slow at me this morning at 9 am GMT +0, I've been able to run all my tests with this new FU version from IntelliJ.
> >
> > Out of the IDE, my build system for this app is done with Rake (ruby) and use a Runner app which once compile is launched by ADL, for this one, I had:
> >
> > VerifyError: Error #1053: Illegal override of generateMXMLInstances in mx.containers.ViewStack.
> >
> > at flash.display::MovieClip/nextFrame()
> > at mx.managers::SystemManager/deferredNextFrame()[E:\dev\4.y\frameworks\projects\framework\src\mx\managers\SystemManager.as:278]
> > at mx.managers::SystemManager/preloader_preloaderDocFrameReadyHandler()[E:\dev\4.y\frameworks\projects\framework\src\mx\managers\SystemManager.as:2627]
> > at flash.events::EventDispatcher/dispatchEventFunction()
> > at flash.events::EventDispatcher/dispatchEvent()
> > at mx.preloaders::Preloader/timerHandler()[E:\dev\4.y\frameworks\projects\framework\src\mx\preloaders\Preloader.as:515]
> > at flash.utils::Timer/_timerDispatch()
> > at flash.utils::Timer/tick()
> >
> > after running 4.6.0.23201/bin/adl bin/test/DesktopRunner-app.xml
> >
> > I've already seen this error somewhere but I forgot where though, did I miss something ?
> >
> > Note: I didn't test with flexcover.
> >
> > Thanks,
> > Frédéric THOMAS
> >
> > [1] https://repository.apache.org/content/repositories/orgapacheflex-1010/
> >
> > > From: christofer.dutz@c-ware.de
> > > To: dev@flex.apache.org
> > > Subject: AW: [LAST CALL] FlexUnit 4.3
> > > Date: Thu, 2 Apr 2015 07:45:22 +0000
> > >
> > > The staging repo is for the playing around ... the source package is needed for the release. I didn't quite see the point in deploying the source package to the Nexus as the source package is released otherwise.
> > >
> > > Chris
> > >
> > > ________________________________________
> > > Von: Justin Mclean <ju...@classsoftware.com>
> > > Gesendet: Donnerstag, 2. April 2015 00:22
> > > An: dev@flex.apache.org
> > > Betreff: Re: [LAST CALL] FlexUnit 4.3
> > >
> > > Hi,
> > >
> > > > Ok so I staged the Maven output at https://repository.apache.org/content/repositories/orgapacheflex-1010/
> > >
> > > Is there a source package there? I couldn't find one to review.
> > >
> > > Thanks,
> > > Justin
> >
>
RE: AW: AW: [LAST CALL] FlexUnit 4.3
Posted by Frédéric THOMAS <we...@hotmail.com>.
Hi Chris,
Yes, with the 4.6 but was pretty sure to remember that I used the FU 4.2 with my last 4.6 project (maven) and worked fine, maybe I've got a bad memory.
> Did we change anything signifficantly?
I'm not sure but that's pity if it means it won't work with the 4.6
Frédéric THOMAS
> From: christofer.dutz@c-ware.de
> To: dev@flex.apache.org
> Subject: AW: AW: [LAST CALL] FlexUnit 4.3
> Date: Thu, 2 Apr 2015 10:18:19 +0000
>
>
> Hi Frederic,
>
> well I think FlexUnit is compiled with Flex 4.12 (At least I think this is what I could see in the Ant scripts) ... in the End I think it will use whatever is located in the FLEX_HOME variable (Which is a 4.13 for the system I built the artifacts from). Judging from your message I would assume you let it run with 4.6, am I correct? Did we change anything signifficantly?
>
> Chris
>
>
>
> ________________________________________
> Von: Frédéric THOMAS <we...@hotmail.com>
> Gesendet: Donnerstag, 2. April 2015 10:53
> An: dev@flex.apache.org
> Betreff: RE: AW: [LAST CALL] FlexUnit 4.3
>
> Hi,
>
> Except the site [1] was extremely slow at me this morning at 9 am GMT +0, I've been able to run all my tests with this new FU version from IntelliJ.
>
> Out of the IDE, my build system for this app is done with Rake (ruby) and use a Runner app which once compile is launched by ADL, for this one, I had:
>
> VerifyError: Error #1053: Illegal override of generateMXMLInstances in mx.containers.ViewStack.
>
> at flash.display::MovieClip/nextFrame()
> at mx.managers::SystemManager/deferredNextFrame()[E:\dev\4.y\frameworks\projects\framework\src\mx\managers\SystemManager.as:278]
> at mx.managers::SystemManager/preloader_preloaderDocFrameReadyHandler()[E:\dev\4.y\frameworks\projects\framework\src\mx\managers\SystemManager.as:2627]
> at flash.events::EventDispatcher/dispatchEventFunction()
> at flash.events::EventDispatcher/dispatchEvent()
> at mx.preloaders::Preloader/timerHandler()[E:\dev\4.y\frameworks\projects\framework\src\mx\preloaders\Preloader.as:515]
> at flash.utils::Timer/_timerDispatch()
> at flash.utils::Timer/tick()
>
> after running 4.6.0.23201/bin/adl bin/test/DesktopRunner-app.xml
>
> I've already seen this error somewhere but I forgot where though, did I miss something ?
>
> Note: I didn't test with flexcover.
>
> Thanks,
> Frédéric THOMAS
>
> [1] https://repository.apache.org/content/repositories/orgapacheflex-1010/
>
> > From: christofer.dutz@c-ware.de
> > To: dev@flex.apache.org
> > Subject: AW: [LAST CALL] FlexUnit 4.3
> > Date: Thu, 2 Apr 2015 07:45:22 +0000
> >
> > The staging repo is for the playing around ... the source package is needed for the release. I didn't quite see the point in deploying the source package to the Nexus as the source package is released otherwise.
> >
> > Chris
> >
> > ________________________________________
> > Von: Justin Mclean <ju...@classsoftware.com>
> > Gesendet: Donnerstag, 2. April 2015 00:22
> > An: dev@flex.apache.org
> > Betreff: Re: [LAST CALL] FlexUnit 4.3
> >
> > Hi,
> >
> > > Ok so I staged the Maven output at https://repository.apache.org/content/repositories/orgapacheflex-1010/
> >
> > Is there a source package there? I couldn't find one to review.
> >
> > Thanks,
> > Justin
>
AW: AW: [LAST CALL] FlexUnit 4.3
Posted by Christofer Dutz <ch...@c-ware.de>.
Hi Frederic,
well I think FlexUnit is compiled with Flex 4.12 (At least I think this is what I could see in the Ant scripts) ... in the End I think it will use whatever is located in the FLEX_HOME variable (Which is a 4.13 for the system I built the artifacts from). Judging from your message I would assume you let it run with 4.6, am I correct? Did we change anything signifficantly?
Chris
________________________________________
Von: Frédéric THOMAS <we...@hotmail.com>
Gesendet: Donnerstag, 2. April 2015 10:53
An: dev@flex.apache.org
Betreff: RE: AW: [LAST CALL] FlexUnit 4.3
Hi,
Except the site [1] was extremely slow at me this morning at 9 am GMT +0, I've been able to run all my tests with this new FU version from IntelliJ.
Out of the IDE, my build system for this app is done with Rake (ruby) and use a Runner app which once compile is launched by ADL, for this one, I had:
VerifyError: Error #1053: Illegal override of generateMXMLInstances in mx.containers.ViewStack.
at flash.display::MovieClip/nextFrame()
at mx.managers::SystemManager/deferredNextFrame()[E:\dev\4.y\frameworks\projects\framework\src\mx\managers\SystemManager.as:278]
at mx.managers::SystemManager/preloader_preloaderDocFrameReadyHandler()[E:\dev\4.y\frameworks\projects\framework\src\mx\managers\SystemManager.as:2627]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at mx.preloaders::Preloader/timerHandler()[E:\dev\4.y\frameworks\projects\framework\src\mx\preloaders\Preloader.as:515]
at flash.utils::Timer/_timerDispatch()
at flash.utils::Timer/tick()
after running 4.6.0.23201/bin/adl bin/test/DesktopRunner-app.xml
I've already seen this error somewhere but I forgot where though, did I miss something ?
Note: I didn't test with flexcover.
Thanks,
Frédéric THOMAS
[1] https://repository.apache.org/content/repositories/orgapacheflex-1010/
> From: christofer.dutz@c-ware.de
> To: dev@flex.apache.org
> Subject: AW: [LAST CALL] FlexUnit 4.3
> Date: Thu, 2 Apr 2015 07:45:22 +0000
>
> The staging repo is for the playing around ... the source package is needed for the release. I didn't quite see the point in deploying the source package to the Nexus as the source package is released otherwise.
>
> Chris
>
> ________________________________________
> Von: Justin Mclean <ju...@classsoftware.com>
> Gesendet: Donnerstag, 2. April 2015 00:22
> An: dev@flex.apache.org
> Betreff: Re: [LAST CALL] FlexUnit 4.3
>
> Hi,
>
> > Ok so I staged the Maven output at https://repository.apache.org/content/repositories/orgapacheflex-1010/
>
> Is there a source package there? I couldn't find one to review.
>
> Thanks,
> Justin
Re: AW: [LAST CALL] FlexUnit 4.3
Posted by Mihai Chira <mi...@gmail.com>.
> Or better yet... why don't we make FlexUnit part of the SDK?
+1 - it feels like it would make projects more likely to have unit
tests, and it would hopefully make contributions to FlexUnit more
likely.
Re: AW: [LAST CALL] FlexUnit 4.3
Posted by Erik de Bruin <er...@ixsoftware.nl>.
>> These kinds of verify errors indicate mixing different swc versions. All swcs going into a swf must be on the same sdk version otherwise you risk verify errors.
>
> Does that mean that we ideally should release different FlexUnit
> 'versions' to match each Apache Flex SDK version? At least for this
> release, to give each SDK it's own, 'native' FlexUnit? And going
> forward, should we release FlexUnit together with the SDK, and change
> it's versioning to indicate to which SDK it belongs: FlexUnit 4.15.0?
Or better yet... why don't we make FlexUnit part of the SDK?
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
AW: AW: AW: [LAST CALL] FlexUnit 4.3
Posted by Christofer Dutz <ch...@c-ware.de>.
What do you guys think? I would suggest we wait a little till this work is finished and I'll concentrate on unifying the Maven-Deployment targets and as soon as all is in place we'll start the release.
Currently I don't see a reason for us rushing a release. I was just surprized that we didn't have any artifacts in Maven Central.
I'll concentrate on releasing the Mavenizer. After that I'll spin a Flexmojos release and then we'll come back to FlexUnit.
Chris
-----Ursprüngliche Nachricht-----
Von: Michael A. Labriola [mailto:labriola@digitalprimates.net]
Gesendet: Freitag, 3. April 2015 17:49
An: dev@flex.apache.org
Betreff: RE: AW: AW: [LAST CALL] FlexUnit 4.3
I could be wrong but I suspect the core of flexunit doesn't have sdk dependencies. The CI functions can run without a gui.
>Correct. The FlexUnit core is just AS but there are hooks for the GUI. Its honestly something I wanted to refactor more. Right now it's possible to build a version with or without framework dependencies. I kind of hate that part of it all.
The question may be whether the gui needs to be in the same swf or application domain of the thing it is testing. In theory it would be better to have independence so the gui doesn't impact what is being tested. Don't know if the verify errors indicate a setup issue or something that could be changed.
>This was actually what I was working on originally. The work is about 80% done because having the UIListener in the same application domain as the test does cause issues. Inside the framework you can see a fair amount of work on separating these already but there were some final bridges I was trying to cross on interrogating objects with describe type across application domains. This led me to trying to make the UIListener run in one app domain but the actual test runner in the same domain as the tests. This is viable but the current UIListener uses typed objects, so that needs to be resolved.
RE: AW: AW: [LAST CALL] FlexUnit 4.3
Posted by "Michael A. Labriola" <la...@digitalprimates.net>.
I could be wrong but I suspect the core of flexunit doesn't have sdk dependencies. The CI functions can run without a gui.
>Correct. The FlexUnit core is just AS but there are hooks for the GUI. Its honestly something I wanted to refactor more. Right now it's possible to build a version with or without framework dependencies. I kind of hate that part of it all.
The question may be whether the gui needs to be in the same swf or application domain of the thing it is testing. In theory it would be better to have independence so the gui doesn't impact what is being tested. Don't know if the verify errors indicate a setup issue or something that could be changed.
>This was actually what I was working on originally. The work is about 80% done because having the UIListener in the same application domain as the test does cause issues. Inside the framework you can see a fair amount of work on separating these already but there were some final bridges I was trying to cross on interrogating objects with describe type across application domains. This led me to trying to make the UIListener run in one app domain but the actual test runner in the same domain as the tests. This is viable but the current UIListener uses typed objects, so that needs to be resolved.
Re: AW: AW: [LAST CALL] FlexUnit 4.3
Posted by Alex Harui <ah...@adobe.com>.
I could be wrong but I suspect the core of flexunit doesn't have sdk dependencies. The CI functions can run without a gui.
The question may be whether the gui needs to be in the same swf or application domain of the thing it is testing. In theory it would be better to have independence so the gui doesn't impact what is being tested. Don't know if the verify errors indicate a setup issue or something that could be changed.
It would be better for flexunit to be independent of sdk version in the test subject.
Sent from my LG G3, an AT&T 4G LTE smartphone
------ Original message------
From: Christofer Dutz
Date: Fri, Apr 3, 2015 5:59 AM
To: dev@flex.apache.org;
Subject:AW: AW: [LAST CALL] FlexUnit 4.3
Hmmm, but this way an old SDK won‘t be able to recieve updates to the unit-test framework.
I think we shouldn't put everything in the sdk and give users the choice.
I think there were several packages available ... eventually we could do a normal build that works with most recent FDKs and one with "classifier" "legacy" package for older FDKs.
During a normal release ... where would you download the source package? From the jenkins workspace? If yes, I could setup such a job.
Chris
-----Ursprüngliche Nachricht-----
Von: Erik de Bruin [mailto:erik@ixsoftware.nl]
Gesendet: Freitag, 3. April 2015 07:57
An: dev@flex.apache.org
Cc: webdoublefx@hotmail.com
Betreff: Re: AW: [LAST CALL] FlexUnit 4.3
> These kinds of verify errors indicate mixing different swc versions. All swcs going into a swf must be on the same sdk version otherwise you risk verify errors.
Does that mean that we ideally should release different FlexUnit 'versions' to match each Apache Flex SDK version? At least for this release, to give each SDK it's own, 'native' FlexUnit? And going forward, should we release FlexUnit together with the SDK, and change it's versioning to indicate to which SDK it belongs: FlexUnit 4.15.0?
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl<http://www.ixsoftware.nl>
Re: AW: [LAST CALL] FlexUnit 4.3
Posted by Erik de Bruin <er...@ixsoftware.nl>.
> During a normal release ... where would you download the source package? From the jenkins workspace? If yes, I could setup such a job.
Correct. For the SDK there is a 'nightly' build during dev and a
'release' build on Jenkins during the RC period (after LAST CALL) that
contains both the source and binary packages.
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
AW: AW: [LAST CALL] FlexUnit 4.3
Posted by Christofer Dutz <ch...@c-ware.de>.
Hmmm, but this way an old SDK won‘t be able to recieve updates to the unit-test framework.
I think we shouldn't put everything in the sdk and give users the choice.
I think there were several packages available ... eventually we could do a normal build that works with most recent FDKs and one with "classifier" "legacy" package for older FDKs.
During a normal release ... where would you download the source package? From the jenkins workspace? If yes, I could setup such a job.
Chris
-----Ursprüngliche Nachricht-----
Von: Erik de Bruin [mailto:erik@ixsoftware.nl]
Gesendet: Freitag, 3. April 2015 07:57
An: dev@flex.apache.org
Cc: webdoublefx@hotmail.com
Betreff: Re: AW: [LAST CALL] FlexUnit 4.3
> These kinds of verify errors indicate mixing different swc versions. All swcs going into a swf must be on the same sdk version otherwise you risk verify errors.
Does that mean that we ideally should release different FlexUnit 'versions' to match each Apache Flex SDK version? At least for this release, to give each SDK it's own, 'native' FlexUnit? And going forward, should we release FlexUnit together with the SDK, and change it's versioning to indicate to which SDK it belongs: FlexUnit 4.15.0?
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: AW: [LAST CALL] FlexUnit 4.3
Posted by Erik de Bruin <er...@ixsoftware.nl>.
> These kinds of verify errors indicate mixing different swc versions. All swcs going into a swf must be on the same sdk version otherwise you risk verify errors.
Does that mean that we ideally should release different FlexUnit
'versions' to match each Apache Flex SDK version? At least for this
release, to give each SDK it's own, 'native' FlexUnit? And going
forward, should we release FlexUnit together with the SDK, and change
it's versioning to indicate to which SDK it belongs: FlexUnit 4.15.0?
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: AW: [LAST CALL] FlexUnit 4.3
Posted by Alex Harui <ah...@adobe.com>.
These kinds of verify errors indicate mixing different swc versions. All swcs going into a swf must be on the same sdk version otherwise you risk verify errors.
Sent from my LG G3, an AT&T 4G LTE smartphone
------ Original message------
From: Frédéric THOMAS
Date: Thu, Apr 2, 2015 1:54 AM
To: dev@flex.apache.org;
Subject:RE: AW: [LAST CALL] FlexUnit 4.3
Hi,
Except the site [1] was extremely slow at me this morning at 9 am GMT +0, I've been able to run all my tests with this new FU version from IntelliJ.
Out of the IDE, my build system for this app is done with Rake (ruby) and use a Runner app which once compile is launched by ADL, for this one, I had:
VerifyError: Error #1053: Illegal override of generateMXMLInstances in mx.containers.ViewStack.
at flash.display::MovieClip/nextFrame()
at mx.managers::SystemManager/deferredNextFrame()[E:\dev\4.y\frameworks\projects\framework\src\mx\managers\SystemManager.as:278]
at mx.managers::SystemManager/preloader_preloaderDocFrameReadyHandler()[E:\dev\4.y\frameworks\projects\framework\src\mx\managers\SystemManager.as:2627]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at mx.preloaders::Preloader/timerHandler()[E:\dev\4.y\frameworks\projects\framework\src\mx\preloaders\Preloader.as:515]
at flash.utils::Timer/_timerDispatch()
at flash.utils::Timer/tick()
after running 4.6.0.23201/bin/adl bin/test/DesktopRunner-app.xml
I've already seen this error somewhere but I forgot where though, did I miss something ?
Note: I didn't test with flexcover.
Thanks,
Frédéric THOMAS
[1] https://repository.apache.org/content/repositories/orgapacheflex-1010/
> From: christofer.dutz@c-ware.de
> To: dev@flex.apache.org
> Subject: AW: [LAST CALL] FlexUnit 4.3
> Date: Thu, 2 Apr 2015 07:45:22 +0000
>
> The staging repo is for the playing around ... the source package is needed for the release. I didn't quite see the point in deploying the source package to the Nexus as the source package is released otherwise.
>
> Chris
>
> ________________________________________
> Von: Justin Mclean <ju...@classsoftware.com>
> Gesendet: Donnerstag, 2. April 2015 00:22
> An: dev@flex.apache.org
> Betreff: Re: [LAST CALL] FlexUnit 4.3
>
> Hi,
>
> > Ok so I staged the Maven output at https://repository.apache.org/content/repositories/orgapacheflex-1010/
>
> Is there a source package there? I couldn't find one to review.
>
> Thanks,
> Justin
RE: AW: [LAST CALL] FlexUnit 4.3
Posted by Frédéric THOMAS <we...@hotmail.com>.
Hi,
Except the site [1] was extremely slow at me this morning at 9 am GMT +0, I've been able to run all my tests with this new FU version from IntelliJ.
Out of the IDE, my build system for this app is done with Rake (ruby) and use a Runner app which once compile is launched by ADL, for this one, I had:
VerifyError: Error #1053: Illegal override of generateMXMLInstances in mx.containers.ViewStack.
at flash.display::MovieClip/nextFrame()
at mx.managers::SystemManager/deferredNextFrame()[E:\dev\4.y\frameworks\projects\framework\src\mx\managers\SystemManager.as:278]
at mx.managers::SystemManager/preloader_preloaderDocFrameReadyHandler()[E:\dev\4.y\frameworks\projects\framework\src\mx\managers\SystemManager.as:2627]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at mx.preloaders::Preloader/timerHandler()[E:\dev\4.y\frameworks\projects\framework\src\mx\preloaders\Preloader.as:515]
at flash.utils::Timer/_timerDispatch()
at flash.utils::Timer/tick()
after running 4.6.0.23201/bin/adl bin/test/DesktopRunner-app.xml
I've already seen this error somewhere but I forgot where though, did I miss something ?
Note: I didn't test with flexcover.
Thanks,
Frédéric THOMAS
[1] https://repository.apache.org/content/repositories/orgapacheflex-1010/
> From: christofer.dutz@c-ware.de
> To: dev@flex.apache.org
> Subject: AW: [LAST CALL] FlexUnit 4.3
> Date: Thu, 2 Apr 2015 07:45:22 +0000
>
> The staging repo is for the playing around ... the source package is needed for the release. I didn't quite see the point in deploying the source package to the Nexus as the source package is released otherwise.
>
> Chris
>
> ________________________________________
> Von: Justin Mclean <ju...@classsoftware.com>
> Gesendet: Donnerstag, 2. April 2015 00:22
> An: dev@flex.apache.org
> Betreff: Re: [LAST CALL] FlexUnit 4.3
>
> Hi,
>
> > Ok so I staged the Maven output at https://repository.apache.org/content/repositories/orgapacheflex-1010/
>
> Is there a source package there? I couldn't find one to review.
>
> Thanks,
> Justin
AW: [LAST CALL] FlexUnit 4.3
Posted by Christofer Dutz <ch...@c-ware.de>.
The staging repo is for the playing around ... the source package is needed for the release. I didn't quite see the point in deploying the source package to the Nexus as the source package is released otherwise.
Chris
________________________________________
Von: Justin Mclean <ju...@classsoftware.com>
Gesendet: Donnerstag, 2. April 2015 00:22
An: dev@flex.apache.org
Betreff: Re: [LAST CALL] FlexUnit 4.3
Hi,
> Ok so I staged the Maven output at https://repository.apache.org/content/repositories/orgapacheflex-1010/
Is there a source package there? I couldn't find one to review.
Thanks,
Justin
Re: [LAST CALL] FlexUnit 4.3
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> Ok so I staged the Maven output at https://repository.apache.org/content/repositories/orgapacheflex-1010/
Is there a source package there? I couldn't find one to review.
Thanks,
Justin
AW: [LAST CALL] FlexUnit 4.3
Posted by Christofer Dutz <ch...@c-ware.de>.
And regarding examples ... the FlexUnit project does have a FlexUnit4SampleCIProject or FlexUnit4Turnkey as well as FlexUnit4Tutorials Projects which should answer all questions about how to use FlexUnit (the CIProject seems to have an Ant config as well as a Maven config that seem to both use Flexunit).
Chris
________________________________________
Von: Christofer Dutz <ch...@c-ware.de>
Gesendet: Mittwoch, 1. April 2015 13:25
An: dev@flex.apache.org
Betreff: AW: [LAST CALL] FlexUnit 4.3
Ok so I staged the Maven output at https://repository.apache.org/content/repositories/orgapacheflex-1010/
So feel free to evaluate it. I have looked at how to configure the jenkins, but currently the build wouldn't support nightly SNAPSHOT versions. I guess this was the first project for which I created an Ant script for publishing Maven artifacts. I have done this for several other projects now and created a far more solid approach (Which I already added to other Flex Modules). I'll switch FlexUnit to using this script instead of the current one as soon as I find the time. Currently the job does it's job good enough though so I don't want do to this prior to releasing 4.3.
I would like to create a sub-directory in our flex-utils repo in which I would add a "maven.xml" ant script with documentation that we can use in several projects ... no need to re-invent the wheel for every Ant module.
Chris
________________________________________
Von: Christofer Dutz <ch...@c-ware.de>
Gesendet: Mittwoch, 1. April 2015 09:18
An: dev@flex.apache.org
Betreff: AW: [LAST CALL] FlexUnit 4.3
Hi Alex,
I didn't explicitly set one up, but I could do that. All I did was to add the Maven artifact generation, signing and deployment stuff to the build. If it's ok with you I could change the current version from 4.3.0 to 4.3.0-SNAPSHOT and have an automatic build job that also deploys the Maven artifacts to the snapshot repo.
Chris
________________________________________
Von: Alex Harui <ah...@adobe.com>
Gesendet: Mittwoch, 1. April 2015 06:33
An: dev@flex.apache.org
Betreff: Re: [LAST CALL] FlexUnit 4.3
Hi Chris,
Is there a nightly build we can examine? Or maybe put something out on
staging but don’t call a vote. The idea is that we’re supposed to iron
out the issues before cutting an official RC.
Also, how do we use/test the code?
Thanks,
-Alex
On 3/30/15, 6:08 AM, "Mihai Chira" <mi...@gmail.com> wrote:
>Hi Chris,
>
>
>I'm very much looking forward to this. Then we'll be able to get our
>test runner to use this version[1], which should finally get
>FLEX_34625_Tests to pass.
>
>
>[1] http://s.apache.org/GKN
>
>
>On 30 March 2015 at 13:22, Christofer Dutz <ch...@c-ware.de>
>wrote:
>> Hi,
>>
>>
>> I am preparing to start a new release of FlexUnit. Even if only a
>>hand-full of bugs were fixed, this time I am intending on also releasing
>>the Maven artifacts for FlexUnit so I think it's worth a 4.3 :-)
>>
>>
>> Eventually (depending on the german wether during the Easter public
>>holidays) I'm planning on staging the RC next Monday. So if you have
>>anything to go into the package ... get started right away :-)
>>
>>
>> Chris
AW: [LAST CALL] FlexUnit 4.3
Posted by Christofer Dutz <ch...@c-ware.de>.
Ok so I staged the Maven output at https://repository.apache.org/content/repositories/orgapacheflex-1010/
So feel free to evaluate it. I have looked at how to configure the jenkins, but currently the build wouldn't support nightly SNAPSHOT versions. I guess this was the first project for which I created an Ant script for publishing Maven artifacts. I have done this for several other projects now and created a far more solid approach (Which I already added to other Flex Modules). I'll switch FlexUnit to using this script instead of the current one as soon as I find the time. Currently the job does it's job good enough though so I don't want do to this prior to releasing 4.3.
I would like to create a sub-directory in our flex-utils repo in which I would add a "maven.xml" ant script with documentation that we can use in several projects ... no need to re-invent the wheel for every Ant module.
Chris
________________________________________
Von: Christofer Dutz <ch...@c-ware.de>
Gesendet: Mittwoch, 1. April 2015 09:18
An: dev@flex.apache.org
Betreff: AW: [LAST CALL] FlexUnit 4.3
Hi Alex,
I didn't explicitly set one up, but I could do that. All I did was to add the Maven artifact generation, signing and deployment stuff to the build. If it's ok with you I could change the current version from 4.3.0 to 4.3.0-SNAPSHOT and have an automatic build job that also deploys the Maven artifacts to the snapshot repo.
Chris
________________________________________
Von: Alex Harui <ah...@adobe.com>
Gesendet: Mittwoch, 1. April 2015 06:33
An: dev@flex.apache.org
Betreff: Re: [LAST CALL] FlexUnit 4.3
Hi Chris,
Is there a nightly build we can examine? Or maybe put something out on
staging but don’t call a vote. The idea is that we’re supposed to iron
out the issues before cutting an official RC.
Also, how do we use/test the code?
Thanks,
-Alex
On 3/30/15, 6:08 AM, "Mihai Chira" <mi...@gmail.com> wrote:
>Hi Chris,
>
>
>I'm very much looking forward to this. Then we'll be able to get our
>test runner to use this version[1], which should finally get
>FLEX_34625_Tests to pass.
>
>
>[1] http://s.apache.org/GKN
>
>
>On 30 March 2015 at 13:22, Christofer Dutz <ch...@c-ware.de>
>wrote:
>> Hi,
>>
>>
>> I am preparing to start a new release of FlexUnit. Even if only a
>>hand-full of bugs were fixed, this time I am intending on also releasing
>>the Maven artifacts for FlexUnit so I think it's worth a 4.3 :-)
>>
>>
>> Eventually (depending on the german wether during the Easter public
>>holidays) I'm planning on staging the RC next Monday. So if you have
>>anything to go into the package ... get started right away :-)
>>
>>
>> Chris
AW: [LAST CALL] FlexUnit 4.3
Posted by Christofer Dutz <ch...@c-ware.de>.
Hi Alex,
I didn't explicitly set one up, but I could do that. All I did was to add the Maven artifact generation, signing and deployment stuff to the build. If it's ok with you I could change the current version from 4.3.0 to 4.3.0-SNAPSHOT and have an automatic build job that also deploys the Maven artifacts to the snapshot repo.
Chris
________________________________________
Von: Alex Harui <ah...@adobe.com>
Gesendet: Mittwoch, 1. April 2015 06:33
An: dev@flex.apache.org
Betreff: Re: [LAST CALL] FlexUnit 4.3
Hi Chris,
Is there a nightly build we can examine? Or maybe put something out on
staging but don’t call a vote. The idea is that we’re supposed to iron
out the issues before cutting an official RC.
Also, how do we use/test the code?
Thanks,
-Alex
On 3/30/15, 6:08 AM, "Mihai Chira" <mi...@gmail.com> wrote:
>Hi Chris,
>
>
>I'm very much looking forward to this. Then we'll be able to get our
>test runner to use this version[1], which should finally get
>FLEX_34625_Tests to pass.
>
>
>[1] http://s.apache.org/GKN
>
>
>On 30 March 2015 at 13:22, Christofer Dutz <ch...@c-ware.de>
>wrote:
>> Hi,
>>
>>
>> I am preparing to start a new release of FlexUnit. Even if only a
>>hand-full of bugs were fixed, this time I am intending on also releasing
>>the Maven artifacts for FlexUnit so I think it's worth a 4.3 :-)
>>
>>
>> Eventually (depending on the german wether during the Easter public
>>holidays) I'm planning on staging the RC next Monday. So if you have
>>anything to go into the package ... get started right away :-)
>>
>>
>> Chris
Re: [LAST CALL] FlexUnit 4.3
Posted by Alex Harui <ah...@adobe.com>.
Hi Chris,
Is there a nightly build we can examine? Or maybe put something out on
staging but don’t call a vote. The idea is that we’re supposed to iron
out the issues before cutting an official RC.
Also, how do we use/test the code?
Thanks,
-Alex
On 3/30/15, 6:08 AM, "Mihai Chira" <mi...@gmail.com> wrote:
>Hi Chris,
>
>
>I'm very much looking forward to this. Then we'll be able to get our
>test runner to use this version[1], which should finally get
>FLEX_34625_Tests to pass.
>
>
>[1] http://s.apache.org/GKN
>
>
>On 30 March 2015 at 13:22, Christofer Dutz <ch...@c-ware.de>
>wrote:
>> Hi,
>>
>>
>> I am preparing to start a new release of FlexUnit. Even if only a
>>hand-full of bugs were fixed, this time I am intending on also releasing
>>the Maven artifacts for FlexUnit so I think it's worth a 4.3 :-)
>>
>>
>> Eventually (depending on the german wether during the Easter public
>>holidays) I'm planning on staging the RC next Monday. So if you have
>>anything to go into the package ... get started right away :-)
>>
>>
>> Chris
Re: [LAST CALL] FlexUnit 4.3
Posted by Mihai Chira <mi...@gmail.com>.
Hi Chris,
I'm very much looking forward to this. Then we'll be able to get our
test runner to use this version[1], which should finally get
FLEX_34625_Tests to pass.
[1] http://s.apache.org/GKN
On 30 March 2015 at 13:22, Christofer Dutz <ch...@c-ware.de> wrote:
> Hi,
>
>
> I am preparing to start a new release of FlexUnit. Even if only a hand-full of bugs were fixed, this time I am intending on also releasing the Maven artifacts for FlexUnit so I think it's worth a 4.3 :-)
>
>
> Eventually (depending on the german wether during the Easter public holidays) I'm planning on staging the RC next Monday. So if you have anything to go into the package ... get started right away :-)
>
>
> Chris