By PVG viagra

Usually money Payday loans quickly for some
Feb
16
FUnit Framework Update 0.70.0383
Filed Under (Updates) by Ryan Christiansen on 02-16-2009

The next major revision to the framework core is now available for download. Release 0.70 provides significant enhancements in three key areas:

  • GUI Support
  • Test Automation
  • Automated Builds and Continuous Integration

GUI Test Runner

Although a forthcoming enhanced UI was detailed in the framework roadmap, community feedback indicated that a GUI was critical, even in the earliest development stages. I had admittedly focused more on the NUnit feature set, rather than front-end usability. Not surprisingly, certain aspects of a .NET approach stifled the strengths of the Flash environment making GUI development cumbersome at best. This release addressed several of these limitations.

The SimpleTestRunner was designed for use with automated testing where visual feedback is useful but little interactivity is required.

A more advanced testing interface, such as the FlexUnit GUI shown here, is actively underway.

Continuous Integration Support for TeamCity

On of the most exciting aspects of Release 0.70 is that the build was fully automated start to finish. That means that the SVN checkout, ANT builds, FUnit testing with results, and final zipped distributions were all done automatically by my TeamCity build server.

FUnit Tests in TeamCity

It is important to note that TeamCity is not just running the tests, it is ingesting live data and displays detailed information about test results and failures as they occur. Click here to have a closer look.

Read More    (8) Comments


Comments:
8 Comments posted on "FUnit Framework Update 0.70.0383"
Marc Kassay on March 19th, 2009 at 11:00 am #

Hi.
After editing ‘common.properties’ file to reflect my computer setup, I was able to compile FUnitProject from the ‘samples’ sub-directory, from Flex Builder 3.0. However, when I CTRL+click on any class from ‘funit’ or ‘sv’ package, I get a code navigation error. I am not sure why this is, since I can see the SWCs in the libs folder from FlexBuilder’s Navigation panel.


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 #

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.


Marc Kassay on March 21st, 2009 at 11:46 am #

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


Hellen Clark on March 26th, 2009 at 7:02 pm #

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


Peri on April 22nd, 2009 at 6:58 am #

Good post.


Luiz Rolim on May 17th, 2009 at 8:16 pm #

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?


Ryan Christiansen on May 19th, 2009 at 7:26 am #

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


Post a comment

Name: 
Email: 
URL: 
Comments: 

.