In the FlexUnit wiki I've read about the very interesting SequenceRunner that was contributed by the Fluint folks. Now I am trying to run a test that is very similar to the example, however when executing the run() Method of the SequenceRunner instance, I get this exception:
Cannot add asynchronous functionality to methods defined by Test,Before or After that are not marked async
Error: Cannot add asynchronous functionality to methods defined by Test,Before or After that are not marked async at org.flexunit.async::AsyncLocator$/getCallableForTest()[C:Usersdmoor eDocuments\_ProductionFlex Unit 4GITFlexUnit4srcorgflexunitasyncAsyncLocator.as:82]
I've recently started practising test driven development - thus far I've been working on a library project, so I've organised my FlexUnit tests in a separate FlexBuilder 3 project, linking against my library's swc.Now I'm working on a web app and wondering how best to organise the tests for this. At the moment I've put them in a src/test package in the project I'm testing, with the test runner application at the same level as the default application. Is this the best way to do it, or should I have a separate test project and link in the source for the application I'm testing?
I needed some guidance on how to use FlexUnit 4 within Flash Builder,to unit test a Parsley-frameworked Flex application.I have tried lookign at one or two sites but with no avail.
I am building an app using ActionScript3 with Flash Builder 4 as my IDE.
The IDE supports a unit testing framework called "FlexUnit".
I can build and run tests within the IDE, no problem.
After much pain and suffering I figured out how to build the unit tests as a swf from the command line. I can point a browser or flash player at the swf and the tests run.
But for an automated build system this is no good: I would like to build the tests, run them, and collect/analyze the results to tell which tests, if any, are failing.
I can imaging some hackery: hack FlexUnit base libraries to dump output to stderr instead of just to the IDE console. Hack some script together that points a browser at the swf, counts to 60, kills the browser and checks stderr.
But that's hideous.
I have to believe there's some way to build and run from the command line that works nicely with automated build systems.
Further complication: I am a relative noob with ActionScript (~1 month). My background is C++, makefiles, etc. All the stuff I had to do to get the tests even to build outside the ide (a build.xml file, ant) was complete greek to me, just cut n pasting from examples I could find.
I am using FlexUnit4 with FlashBuilder4. A lot of the classes that I'm unit testing make use of the Flash Logger.In the main app, we use TraceTarget so that the logging shows up in the trace window, which greatly aids in debugging:[code]I'd like to do the same thing for the unit test runner that FlashBuilder generates (FlexUnitApplication.mxml), but I'm not sure how to go about it. I could, of course, add TraceTarget to FlexUnit Application. mxml, but as the warning at the top of the file says,My question is: how do I get logging-to-trace to work with FlashBuilder and FlexUnit?
confirm that Flash Builder 4 STANDARD comes bundled with FlexUnit 4 just like Flash Builder 4 Premium trial does? My company is interested in buying a few copies just for unit testing an existing code base. Don't want to spend the extra money if not necessary and Adobe support was completely useless. Also, any other considerations you can think of regarding Flash Builder 4 Standard & FlexUnit 4?
Can I use FlexUnit to unit test a File Upload and delete? Are those actions good examples of unit testing? I'm a little new to unit testing and trying to figure out what parts of my UI are suitable for unit tests.
I am testing timerevent with flex unit. Follwing is the code which i tried ,it always goes to cmdFailed function (Time out function).I am new to flex unit.[code]
I've set up FlexUnit in my app, I want to debug a test using trace, but im not sure how to get flexunit to traceto the flashlog file. Here's part of my test task in ant, I thought the 'localtrusted' property would help, but it doesnt seem to. In my logs I get the testcases only, none of my traces which are inside my tests.
In FlexUnit 1 it is possible to access the name of the currently-running test using the TestCase.getName() method because all tests subclass TestCase. In FlexUnit 4, however, there's no base class for tests; the tests are identified by annotations. So, how can I replicate the getName() functionality in FlexUnit 4?