Comments for FUnit Testing Framework

Comment on FlexCover – Finally Code Coverage for Flex by mouli

mouli — Fri, 05 Mar 2010 10:04:56 +0000

This helps me in knowing about Flexcoverage …. can u please send me more details about Flexcover ( i am interested in working with Flexcover)

Comment on Round 2: xUnit ‘assertEquals’ – JUnit/FlexUnit vs. NUnit/FUnit by Miere Teixeira

Miere Teixeira — Mon, 21 Sep 2009 14:32:37 +0000

I really liked your article. It was nice as the other ones here in the blog. But I’d like to focus on this:

“More specifically, I didn’t have the same frustrating experience when using NUnit. Here’s just a couple of ways that NUnit spoiled me.”

You have listed some things that you don’t like in JUnit (consequently in FlexUnit), but have you seen JUnit 4? The Behavior your listed above has been changed in JUnit 4 with Annotations and some statical functions.

Take a look there, and tell me what do you think about its new behavior.

Comment on Continuous Integration with FUnit and TeamCity by MichaellaS

MichaellaS — Tue, 21 Jul 2009 22:30:56 +0000

tks for the effort you put in here I appreciate it!

Comment on FUnit Framework Update 0.70.0383 by Ryan Christiansen

Ryan Christiansen — Tue, 19 May 2009 12:26:25 +0000

Hi Luiz,

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.

http://blog.funit.org/?p=327

Comment on FUnit Framework Update 0.70.0383 by Luiz Rolim

Luiz Rolim — Mon, 18 May 2009 01:16:47 +0000

Hi,

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?

Comment on FUnit Framework Update 0.70.0383 by Peri

Peri — Wed, 22 Apr 2009 11:58:52 +0000

Good post.

Comment on FUnit Framework Update 0.70.0383 by Hellen Clark

Hellen Clark — Fri, 27 Mar 2009 00:02:11 +0000

Good work on your blog, I love to see the effort and I am just saying keep up the good work.

Comment on FUnit Framework Update 0.70.0383 by Marc Kassay

Marc Kassay — Sat, 21 Mar 2009 16:46:15 +0000

Ah…that now works!:)
Thanks for the explanation, as eventually soon I plan to delve into a CI server such as TeamCity.

Comment on FUnit Framework Update 0.70.0383 by Ryan Christiansen

Ryan Christiansen — Sat, 21 Mar 2009 15:10:09 +0000

Hi Marc,

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.

Comment on FUnit Framework Update 0.70.0383 by Marc Kassay

Marc Kassay — Sat, 21 Mar 2009 13:40:20 +0000

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.