How to structure tests within a Flex Builder project

Forum|Forum|17 years ago
December 4, 2008
3 replies
1264 views

I am having difficulty in deciding where to store my FlexUnit tests. I am hoping that someone can provide some 'sage advice' for me. The project is simple. Here is the structure: \bin-debug \src\impl\<several AS files> \src\unit_tests\\<several AS files> \src\main.mxml \src\TestRunner.mxml 'impl' is a package where all of my business logic is stored. 'unit_tests' are where all of my FlexUnit tests are. With this structure my unit tests cannot import and test any classes within the impl package unless I make the classes public instead of private. I do not want to do this since only 2 of the 10 classes within impl should be exposed by design. The others support those 2 top-level classes. I also want the ability to write unit tests for all of my classes, no matter where they reside. I also want to keep my test code separate from my implementation/production code. Could someone please provide some insight on how I can structure the project so that I have unit tests for all of my classes, which are separate from production code?

FlexUnit

This topic has been closed for replies.

_

_Daniel_Rinehart_

Participating Frequently

Edit the project's properties. Under Flex Build Path, on the Source Path tab, select Add Folder. If you need to share projects between people, it's best to define a Linked Resource. You can find more information on Eclipse Linked resources in the Eclipse help system. -- Daniel R. <danielr@neophi.com> [http://danielr.neophi.com/] On Fri, Dec 5, 2008 at 3:59 PM, Sheldon P <member@adobeforums.com> wrote: > A new message was posted by Sheldon P in > > FlexUnit Development -- > How to structure tests within a Flex Builder project > > Thank-you for your reply Daniel. Your post sheds some light on my problem. > > I think the 'source code reference' is my best option. How do I do I create > that reference in Flex Builder?

_

_Sheldon_P_Author

Participant

Thank-you for your reply Daniel. Your post sheds some light on my problem.

I think the 'source code reference' is my best option. How do I do I create that reference in Flex Builder?

_

_Daniel_Rinehart_

Participating Frequently

The general approach I've used is to setup a separate project that contains the test code in a parallel package structure. For example: project\ project\src\main.mxml project\src\impl\* projectTest\ projectTest\src\mainTest.mxml projectTest\src\impl\*Test The Project Test project can then either reference project as a dependent project if it is a library project or use a source code reference if it is an application or a library project. This is mostly a matter of preference depending on how you want your projects to build. The parallel package structure in the test project will let you easily import and test classes in the project under test without having to worry about odd package import issues. -- Daniel R. <danielr@neophi.com> [http://danielr.neophi.com/] On Thu, Dec 4, 2008 at 6:23 PM, Sheldon P <member@adobeforums.com> wrote: > A new discussion was started by Sheldon P in > > FlexUnit Development -- > How to structure tests within a Flex Builder project > > I am having difficulty in deciding where to store my FlexUnit tests. I am > hoping that someone can provide some 'sage advice' for me.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded