6 Comments posted on "FUnit Framework Update 0.70.0383"
Marc Kassay on March 19th, 2009 at 11:00 am #
Marc Kassay on March 21st, 2009 at 8:40 am #
Ok, I figured it out now. I thought that the SWCs had dependencies for them, such as the ‘common.properties’ file, which I would of needed to edit. But I assume that’s to compile a new SWC.
Anyways, I am about four days old with Unit Testing! Your project looks great, I am looking forward to it. Thanks again Ryan.
Ryan Christiansen on March 21st, 2009 at 10:10 am #
The ‘common.properties’ file is only used for ANT compilation. This is useful if you don’t have a FlexBuilder license or if you’re automating your builds with TeamCity, Maven, CruiseControl, etc.
As for your second question. The sample project uses SWC files in the libs directory. This allows you to build without the FUnit or SwirlyVision source projects. Think of a SWC file as a compiled DLL library. It can be used wherever you like but contains no source code.
If you want CTRL+click to work, you have two options.
1. Open the project properties > “Flex Build Path” > “Library Path”. Expand libs/FUnit.swc and you’ll notice “Source attachment: (None)” Simply browse to the FUnit source directory.
- or -
2. Remove the SWC file(s) from the libs directory and instead add the source project ‘FUnit’ and/or ‘SwirlyVision’ to the library path.
Do either of these and you’re all set.
Marc Kassay on March 21st, 2009 at 11:46 am #
Ah…that now works!:)
Luiz Rolim on May 17th, 2009 at 8:16 pm #
I´m trying to move ahead from flexUnit to funit.
Everything was running fine, but i found a issue on the SimpleTestRunner.
How can I know which tests are broken?
Ryan Christiansen on May 19th, 2009 at 7:26 am #
You’re correct. The SimpleTestRunner is very limited but originally intended for automated builds. In the meantime, I’ve prepared another article that may help.
Post a comment