Menu
▾
▴
asunit-users
|
From: Sam <sa...@th...> - 2006-05-15 13:23:44
|
Hello, I've been trying to set up XUL UI on OS X with no luck. The MAC-README says: 1) Download the mac release of xulrunner from: http:// developer.mozilla.org/en/docs/XULRunner 2) Unpack dmg archive from here into a new folder named "xulrunner", so that this directory looks like: I don't understand #2. When I unpack the dmg the result is xulrunner-1.9a1.en-US.mac.pkg. Which will install xulrunner in /Library/Frameworks/XUL.framework/ Is number 2 saying that I should put xulrunner-1.9a1.en-US.mac.pkg in a folder named xulrunner? Thanks for any help |
|
From: Sam L. <sa...@th...> - 2006-05-15 14:03:06
|
Hello, I've been trying to set up XUL UI on OS X with no luck. The MAC-README says: 1) Download the mac release of xulrunner from: http://developer.mozilla.org/en/docs/XULRunner 2) Unpack dmg archive from here into a new folder named "xulrunner", so that this directory looks like: I don't understand #2. When I unpack the dmg the result is xulrunner-1.9a1.en-US.mac.pkg. Which will install xulrunner in /Library/Frameworks/XUL.framework/ Is number 2 saying that I should put xulrunner-1.9a1.en-US.mac.pkg in a folder named xulrunner? Thanks for any help |
|
From: Luke B. <lb...@gm...> - 2006-05-15 16:52:34
|
I'm guessing that .pkg is some kind of mac zip file. Is there a way to further "unpack" it so that you have a series of directories? If so, then there should be a xulrunner folder from our distribution that goes inside of your installed XulRunner location... Please let me know if that doesn't work for you as some folks have offered to get more complete mac installer going and this would probably be a good time to get that published. Thanks, Luke Bayes www.asunit.org |
|
From: Chris A. <mrc...@gm...> - 2006-05-15 14:54:54
|
Hey Sam, I tried messing around with this at one point and noticed that the structure of an XUL application on OSX is different than on Windows. It also requires that you make an document bundle, in order to double click on it. Here is some information that might be useful: http://wiki.mozilla.org/XUL:XUL_Application_Packaging. There is also a tremendous amount of documentation on the subject here: http://www.mozilla.org/projects/xul/ I was never able to get it to work on a Mac though, so if you manage to figure it out, please let us know. I've been pretty happy just making my test cases by hand, but would love to see what this XUL app does. Good luck. -Chris On 5/15/06, Sam <sa...@th...> wrote: > > Hello, > I've been trying to set up XUL UI on OS X with no luck. > > The MAC-README says: > 1) Download the mac release of xulrunner from: > http://developer.mozilla.org/en/docs/XULRunner > 2) Unpack dmg archive from here into a new folder named "xulrunner", so t= hat > this directory looks like: > > I don't understand #2. > When I unpack the dmg the result is xulrunner-1.9a1.en-US.mac.pkg. > Which will install xulrunner in > /Library/Frameworks/XUL.framework/ > > Is number 2 saying that I should put xulrunner-1.9a1.en-US.mac.pkg in a > folder named xulrunner? > > Thanks for any help > > > |
|
From: Sam <sa...@th...> - 2006-05-17 01:19:37
|
Hi Chris, Thanks for your input, I have exhausted trying to figure out the XUL stuff. I would be interested in knowing the process you use when making the test cases by hand. Not specifics on unit testing or anything like that, but after you've built the test how do you run them. The documentation on using just the framework seems, well, non-existant. I am using textmate and the mtasc compiler. Actually I'm using a development process I found here: http://www.unfitforprint.com/articles/2006/01/02/howto-develop-flash- on-mac-osx-with-rake-mtasc-swfmill-and-textmate and I'd love to add testing to the process. Thanks much, any suggestions or tips are appreciated. -Sam On May 15, 2006, at 10:54 AM, Chris Allen wrote: > Hey Sam, > > I tried messing around with this at one point and noticed that the > structure of an XUL application on OSX is different than on Windows. > It also requires that you make an document bundle, in order to double > click on it. Here is some information that might be useful: > http://wiki.mozilla.org/XUL:XUL_Application_Packaging. There is also a > tremendous amount of documentation on the subject here: > http://www.mozilla.org/projects/xul/ > > I was never able to get it to work on a Mac though, so if you manage > to figure it out, please let us know. I've been pretty happy just > making my test cases by hand, but would love to see what this XUL app > does. > > Good luck. > > -Chris > > On 5/15/06, Sam <sa...@th...> wrote: >> >> Hello, >> I've been trying to set up XUL UI on OS X with no luck. >> >> The MAC-README says: >> 1) Download the mac release of xulrunner from: >> http://developer.mozilla.org/en/docs/XULRunner >> 2) Unpack dmg archive from here into a new folder named >> "xulrunner", so that >> this directory looks like: >> >> I don't understand #2. >> When I unpack the dmg the result is xulrunner-1.9a1.en-US.mac.pkg. >> Which will install xulrunner in >> /Library/Frameworks/XUL.framework/ >> >> Is number 2 saying that I should put xulrunner-1.9a1.en-US.mac.pkg >> in a >> folder named xulrunner? >> >> Thanks for any help >> >> >> > > > ------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, > security? > Get stuff done quickly with pre-integrated technology to make your > job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache > Geronimo > http://sel.as-us.falkag.net/sel? > cmd_______________________________________________ > Asunit-users mailing list > Asu...@li... > https://lists.sourceforge.net/lists/listinfo/asunit-users > > |
|
From: Jan H. <za...@ar...> - 2006-05-17 08:23:19
|
Hi Sam,
I've been following this thread and remember that I struggled myself
quite
a bit when trying to get unit testing to work under OSX....
I don't have too much time currently, but here's at least a short
description how to use Asunit with mtasc under OSX:
1. For displaying the results of the testcases / Sys.println
statements use the
'AsUnit Ui.swf' which can be found in the AsUnit-src.zip (or if you
installed Asunit,
it's under
'$HOME/Library/Application Support/Macromedia/Flash 8/en/
Configuration/WindowSWF/AsUnit Ui.swf'
)
Fire this up in a browser window and click the 'Show Sys.println' in
the lower
left corner, then you'll see the output of any Sys.println statements
used in
your code. (Make sure Sys.as from the Asunit package is in your
classpath)
2. Create a Main class for your unit tests like this one:
--------------- SNIP -----------------------------------
class MainUnitTests {
public static function runUnitTests():Void {
var st:SelectedTests = new SelectedTests();
}
}
---------------- SNAP ---------------------------------
3. Create SelectedTests classes for EACH of your packages
Example source folder: src
Example package structure: org
SelectedTests class in ./src:
--------------- SNIP -----------------------------------
import com.asunit.framework.*;
class SelectedTests extends TestSuite {
private var className:String = "SelectedTests";
public function SelectedTests() {
super();
addTest(new org.SelectedTests());
}
}
---------------- SNAP ---------------------------------
SelectedTests class in ./src/org:
--------------- SNIP -----------------------------------
import com.asunit.framework.*;
class org.SelectedTests extends TestSuite {
private var className:String = "org.SelectedTests";
public function SelectedTests() {
super();
addTest(new org.MyClassOneTest());
//addTest(new org.MyClassTwoTest());
}
}
---------------- SNAP ---------------------------------
where MyClassOneTest and MyClassTwoTest are the Asunit Test Classes
containing the unit tests for your classes.
4. In your .swf have the following ActionScript code on a frame AFTER
the
frame where your classes get imported:
--------------- SNIP -----------------------------------
import MainUnitTests;
MainUnitTests.runUnitTests();
---------------- SNAP ---------------------------------
5. Now compile using mtasc:
--------------- SNIP -----------------------------------
/usr/local/bin/mtasc -strict -keep -frame 6 -cp /path/to/your/
classes -swf to/your/swfFile.swf MainUnitTests
---------------- SNAP ---------------------------------
This assumes that your classes get imported at frame 6 of your .swf,
you need to set this to the frame
where your classes should get imported (after the preloader code).
6. Run your .swf and see the results + Sys.println output in 'AsUnit
UI.swf'
7. By commenting / uncommenting the statements in SelectedTests you
can quickly exclude / include
the TestClasses you want to get executed. Just recompile and run,
this will execute the tests.
Hope this helps you to get started.....
I switched from Flash 8 to Eclipse + FDT (http://
fdt.powerflasher.com/) which works really well for me.
Best regards,
Jan Harmsen
On 17-Mai-2006, at 03:19, Sam wrote:
> Hi Chris,
> Thanks for your input, I have exhausted trying to figure out the
> XUL stuff.
> I would be interested in knowing the process you use when making
> the test cases by hand. Not specifics on unit testing or anything
> like that, but after you've built the test how do you run them. The
> documentation on using just the framework seems, well, non-existant.
> I am using textmate and the mtasc compiler. Actually I'm using a
> development process I found here:
> http://www.unfitforprint.com/articles/2006/01/02/howto-develop-
> flash-on-mac-osx-with-rake-mtasc-swfmill-and-textmate
> and I'd love to add testing to the process.
>
> Thanks much, any suggestions or tips are appreciated.
> -Sam
>
|
|
From: Chris A. <mrc...@gm...> - 2006-05-17 13:33:49
|
I have a variation on this that I can share with you soon. Sorry that
I can't do so now, I'm rushing off to a meeting. Will email later.
-Chris
On 5/17/06, Jan Harmsen <za...@ar...> wrote:
>
> Hi Sam,
>
> I've been following this thread and remember that I struggled myself quit=
e
> a bit when trying to get unit testing to work under OSX....
> I don't have too much time currently, but here's at least a short
> description how to use Asunit with mtasc under OSX:
>
>
> 1. For displaying the results of the testcases / Sys.println statements u=
se
> the
> 'AsUnit Ui.swf' which can be found in the AsUnit-src.zip (or if you
> installed Asunit,
> it's under
> '$HOME/Library/Application Support/Macromedia/Flash
> 8/en/Configuration/WindowSWF/AsUnit Ui.swf'
> )
>
> Fire this up in a browser window and click the 'Show Sys.println' in the
> lower
> left corner, then you'll see the output of any Sys.println statements use=
d
> in
> your code. (Make sure Sys.as from the Asunit package is in your classpath=
)
>
>
> 2. Create a Main class for your unit tests like this one:
> --------------- SNIP -----------------------------------
> class MainUnitTests {
>
> public static function runUnitTests():Void {
>
> var st:SelectedTests =3D new SelectedTests();
>
> }
> }
> ---------------- SNAP ---------------------------------
>
>
> 3. Create SelectedTests classes for EACH of your packages
> Example source folder: src
> Example package structure: org
>
> SelectedTests class in ./src:
> --------------- SNIP -----------------------------------
> import com.asunit.framework.*;
>
> class SelectedTests extends TestSuite {
> private var className:String =3D "SelectedTests";
>
> public function SelectedTests() {
> super();
> addTest(new org.SelectedTests());
> }
> }
>
> ---------------- SNAP ---------------------------------
>
>
> SelectedTests class in ./src/org:
> --------------- SNIP -----------------------------------
> import com.asunit.framework.*;
>
> class org.SelectedTests extends TestSuite {
> private var className:String =3D "org.SelectedTests";
>
> public function SelectedTests() {
> super();
> addTest(new org.MyClassOneTest());
> //addTest(new org.MyClassTwoTest());
> }
> }
> ---------------- SNAP ---------------------------------
>
> where MyClassOneTest and MyClassTwoTest are the Asunit Test Classes
> containing the unit tests for your classes.
>
>
> 4. In your .swf have the following ActionScript code on a frame AFTER the
> frame where your classes get imported:
>
> --------------- SNIP -----------------------------------
> import MainUnitTests;
>
> MainUnitTests.runUnitTests();
> ---------------- SNAP ---------------------------------
>
> 5. Now compile using mtasc:
>
> --------------- SNIP -----------------------------------
> /usr/local/bin/mtasc -strict -keep -frame 6 -cp /path/to/your/classes -s=
wf
> to/your/swfFile.swf MainUnitTests
> ---------------- SNAP ---------------------------------
>
> This assumes that your classes get imported at frame 6 of your .swf, you
> need to set this to the frame
> where your classes should get imported (after the preloader code).
>
>
> 6. Run your .swf and see the results + Sys.println output in 'AsUnit UI.s=
wf'
>
> 7. By commenting / uncommenting the statements in SelectedTests you can
> quickly exclude / include
> the TestClasses you want to get executed. Just recompile and run, this wi=
ll
> execute the tests.
>
>
> Hope this helps you to get started.....
> I switched from Flash 8 to Eclipse + FDT (http://fdt.powerflasher.com/)
> which works really well for me.
>
> Best regards,
>
> Jan Harmsen
>
>
>
>
> On 17-Mai-2006, at 03:19, Sam wrote:
>
> Hi Chris,
>
> Thanks for your input, I have exhausted trying to figure out the XUL stuf=
f.
> I would be interested in knowing the process you use when making the test
> cases by hand. Not specifics on unit testing or anything like that, but
> after you've built the test how do you run them. The documentation on usi=
ng
> just the framework seems, well, non-existant.
> I am using textmate and the mtasc compiler. Actually I'm using a developm=
ent
> process I found here:
> http://www.unfitforprint.com/articles/2006/01/02/howto-develop-flash-on-m=
ac-osx-with-rake-mtasc-swfmill-and-textmate
> and I'd love to add testing to the process.
>
> Thanks much, any suggestions or tips are appreciated.
> -Sam
>
>
|
|
From: Chris A. <mrc...@gm...> - 2006-05-17 19:31:01
|
Sam wrote: > > Hi Chris, > > > > Thanks for your input, I have exhausted trying to figure out the XUL st= uff. > > I would be interested in knowing the process you use when making the te= st > > cases by hand. Not specifics on unit testing or anything like that, but > > after you've built the test how do you run them. The documentation on u= sing > > just the framework seems, well, non-existant. > > I am using textmate and the mtasc compiler. Actually I'm using a develo= pment > > process I found here: > > http://www.unfitforprint.com/articles/2006/01/02/howto-develop-flash-on= -mac-osx-with-rake-mtasc-swfmill-and-textmate > > and I'd love to add testing to the process. > > > > Thanks much, any suggestions or tips are appreciated. > > -Sam Sam, I know exactly how you feel. It took me a while to figure this out myself. I posted a little description on my blog about how I've set it up using nothing but ActionScript2, MTASC and AS2Ant. You can see that here: http://blog.ff9900.org/?p=3D5 I hope it helps. -Chris |
|
From: Sam <sa...@th...> - 2006-05-18 15:30:24
|
Chris,
Thanks alot, your proccess works great. I was just about to give up
on the whole thing, so thanks again.
On May 17, 2006, at 9:33 AM, Chris Allen wrote:
> I have a variation on this that I can share with you soon. Sorry that
> I can't do so now, I'm rushing off to a meeting. Will email later.
>
> -Chris
>
> On 5/17/06, Jan Harmsen <za...@ar...> wrote:
>>
>> Hi Sam,
>>
>> I've been following this thread and remember that I struggled
>> myself quite
>> a bit when trying to get unit testing to work under OSX....
>> I don't have too much time currently, but here's at least a short
>> description how to use Asunit with mtasc under OSX:
>>
>>
>> 1. For displaying the results of the testcases / Sys.println
>> statements use
>> the
>> 'AsUnit Ui.swf' which can be found in the AsUnit-src.zip (or if you
>> installed Asunit,
>> it's under
>> '$HOME/Library/Application Support/Macromedia/Flash
>> 8/en/Configuration/WindowSWF/AsUnit Ui.swf'
>> )
>>
>> Fire this up in a browser window and click the 'Show Sys.println'
>> in the
>> lower
>> left corner, then you'll see the output of any Sys.println
>> statements used
>> in
>> your code. (Make sure Sys.as from the Asunit package is in your
>> classpath)
>>
>>
>> 2. Create a Main class for your unit tests like this one:
>> --------------- SNIP -----------------------------------
>> class MainUnitTests {
>>
>> public static function runUnitTests():Void {
>>
>> var st:SelectedTests = new SelectedTests();
>>
>> }
>> }
>> ---------------- SNAP ---------------------------------
>>
>>
>> 3. Create SelectedTests classes for EACH of your packages
>> Example source folder: src
>> Example package structure: org
>>
>> SelectedTests class in ./src:
>> --------------- SNIP -----------------------------------
>> import com.asunit.framework.*;
>>
>> class SelectedTests extends TestSuite {
>> private var className:String = "SelectedTests";
>>
>> public function SelectedTests() {
>> super();
>> addTest(new org.SelectedTests());
>> }
>> }
>>
>> ---------------- SNAP ---------------------------------
>>
>>
>> SelectedTests class in ./src/org:
>> --------------- SNIP -----------------------------------
>> import com.asunit.framework.*;
>>
>> class org.SelectedTests extends TestSuite {
>> private var className:String = "org.SelectedTests";
>>
>> public function SelectedTests() {
>> super();
>> addTest(new org.MyClassOneTest());
>> //addTest(new org.MyClassTwoTest());
>> }
>> }
>> ---------------- SNAP ---------------------------------
>>
>> where MyClassOneTest and MyClassTwoTest are the Asunit Test Classes
>> containing the unit tests for your classes.
>>
>>
>> 4. In your .swf have the following ActionScript code on a frame
>> AFTER the
>> frame where your classes get imported:
>>
>> --------------- SNIP -----------------------------------
>> import MainUnitTests;
>>
>> MainUnitTests.runUnitTests();
>> ---------------- SNAP ---------------------------------
>>
>> 5. Now compile using mtasc:
>>
>> --------------- SNIP -----------------------------------
>> /usr/local/bin/mtasc -strict -keep -frame 6 -cp /path/to/your/
>> classes -swf
>> to/your/swfFile.swf MainUnitTests
>> ---------------- SNAP ---------------------------------
>>
>> This assumes that your classes get imported at frame 6 of
>> your .swf, you
>> need to set this to the frame
>> where your classes should get imported (after the preloader code).
>>
>>
>> 6. Run your .swf and see the results + Sys.println output in
>> 'AsUnit UI.swf'
>>
>> 7. By commenting / uncommenting the statements in SelectedTests
>> you can
>> quickly exclude / include
>> the TestClasses you want to get executed. Just recompile and run,
>> this will
>> execute the tests.
>>
>>
>> Hope this helps you to get started.....
>> I switched from Flash 8 to Eclipse + FDT (http://
>> fdt.powerflasher.com/)
>> which works really well for me.
>>
>> Best regards,
>>
>> Jan Harmsen
>>
>>
>>
>>
>> On 17-Mai-2006, at 03:19, Sam wrote:
>>
>> Hi Chris,
>>
>> Thanks for your input, I have exhausted trying to figure out the
>> XUL stuff.
>> I would be interested in knowing the process you use when making
>> the test
>> cases by hand. Not specifics on unit testing or anything like
>> that, but
>> after you've built the test how do you run them. The documentation
>> on using
>> just the framework seems, well, non-existant.
>> I am using textmate and the mtasc compiler. Actually I'm using a
>> development
>> process I found here:
>> http://www.unfitforprint.com/articles/2006/01/02/howto-develop-
>> flash-on-mac-osx-with-rake-mtasc-swfmill-and-textmate
>> and I'd love to add testing to the process.
>>
>> Thanks much, any suggestions or tips are appreciated.
>> -Sam
>>
>>
>
>
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services,
> security?
> Get stuff done quickly with pre-integrated technology to make your
> job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache
> Geronimo
> http://sel.as-us.falkag.net/sel?
> cmd_______________________________________________
> Asunit-users mailing list
> Asu...@li...
> https://lists.sourceforge.net/lists/listinfo/asunit-users
>
>
|
|
From: Chris A. <mrc...@gm...> - 2006-05-18 16:15:43
|
On 5/18/06, Sam <sa...@th...> wrote: > Chris, > Thanks alot, your proccess works great. I was just about to give up > on the whole thing, so thanks again. > I'm glad that it worked for you. |
|
From: Sam <sa...@th...> - 2006-05-18 18:24:17
|
Just one more question. How do you structure you directories? I'm having a problem figuring out how to import the classes I want to test. Here's my structure: flash/ assets/ libraries/ main/ classes/ com/ LuminicBox/ three60/ ClassIWantToTest.as test/ asunit/ build.properties build.xml MyTestCase.as MyTestRunner.as How do I import ClassIWantToTest.as into MyTestCase.as? Can you back out of the current directory with import? On May 18, 2006, at 12:15 PM, Chris Allen wrote: > On 5/18/06, Sam <sa...@th...> wrote: >> Chris, >> Thanks alot, your proccess works great. I was just about to give up >> on the whole thing, so thanks again. >> > > I'm glad that it worked for you. > > > ------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, > security? > Get stuff done quickly with pre-integrated technology to make your > job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache > Geronimo > http://sel.as-us.falkag.net/sel? > cmd_______________________________________________ > Asunit-users mailing list > Asu...@li... > https://lists.sourceforge.net/lists/listinfo/asunit-users > > |
|
From: Chris A. <mrc...@gm...> - 2006-05-18 21:06:15
|
Hey Sam,
Okay, so in my current structure I have:
- classes
- asunit/all of their stuff...
- org/
- osflash/
- fling/
- tests/
- TestMovieAsset.as
- assets/
- MovieAsset.as
- build/
- alltests,swf
That's simplified of course. ;-)
So, yeah, if you need to test your class, just use import to get it to
see your class, then use it as you see fit in your TestCase.
Here is an excerpt from my TestMovieAsset class:
mport asunit.framework.TestCase;
import org.osflash.fling.util.assets.MovieAsset;
import com.dynamicflash.utils.Delegate;
import org.osflash.fling.util.assets.AssetLoader;
/**
* @author Chris Allen mrc...@gm...
*/
class org.osflash.fling.tests.TestMovieAsset extends TestCase
{
=09private var className:String =3D "org.osflash.fling.tests.TestMovieAsset=
";
=09
=09private var asset:MovieAsset;
etc...
I hope that helps.
-Chirs
On 5/18/06, Sam <sa...@th...> wrote:
> Just one more question.
> How do you structure you directories?
> I'm having a problem figuring out how to import the classes I want to
> test.
>
> Here's my structure:
>
> flash/
> assets/
> libraries/
> main/
> classes/
> com/
> LuminicBox/
> three60/
> ClassIWantToTest.as
> test/
> asunit/
> build.properties
> build.xml
> MyTestCase.as
> MyTestRunner.as
>
> How do I import ClassIWantToTest.as into MyTestCase.as?
> Can you back out of the current directory with import?
>
>
> On May 18, 2006, at 12:15 PM, Chris Allen wrote:
>
> > On 5/18/06, Sam <sa...@th...> wrote:
> >> Chris,
> >> Thanks alot, your proccess works great. I was just about to give up
> >> on the whole thing, so thanks again.
> >>
> >
> > I'm glad that it worked for you.
> >
|
|
From: Sam <sa...@th...> - 2006-05-19 12:03:20
|
Chris,
Thanks so much for you help and insight on how to get this working.
take care
On May 18, 2006, at 5:06 PM, Chris Allen wrote:
> Hey Sam,
>
> Okay, so in my current structure I have:
>
> - classes
> - asunit/all of their stuff...
> - org/
> - osflash/
> - fling/
> - tests/
> - TestMovieAsset.as
> - assets/
> - MovieAsset.as
> - build/
> - alltests,swf
>
> That's simplified of course. ;-)
>
> So, yeah, if you need to test your class, just use import to get it to
> see your class, then use it as you see fit in your TestCase.
>
> Here is an excerpt from my TestMovieAsset class:
>
> mport asunit.framework.TestCase;
> import org.osflash.fling.util.assets.MovieAsset;
> import com.dynamicflash.utils.Delegate;
> import org.osflash.fling.util.assets.AssetLoader;
> /**
> * @author Chris Allen mrc...@gm...
> */
> class org.osflash.fling.tests.TestMovieAsset extends TestCase
> {
>
> private var className:String =
> "org.osflash.fling.tests.TestMovieAsset";
>
> private var asset:MovieAsset;
> etc...
>
> I hope that helps.
>
> -Chirs
>
> On 5/18/06, Sam <sa...@th...> wrote:
>> Just one more question.
>> How do you structure you directories?
>> I'm having a problem figuring out how to import the classes I want to
>> test.
>>
>> Here's my structure:
>>
>> flash/
>> assets/
>> libraries/
>> main/
>> classes/
>> com/
>> LuminicBox/
>> three60/
>> ClassIWantToTest.as
>> test/
>> asunit/
>> build.properties
>> build.xml
>> MyTestCase.as
>> MyTestRunner.as
>>
>> How do I import ClassIWantToTest.as into MyTestCase.as?
>> Can you back out of the current directory with import?
>>
>>
>> On May 18, 2006, at 12:15 PM, Chris Allen wrote:
>>
>> > On 5/18/06, Sam <sa...@th...> wrote:
>> >> Chris,
>> >> Thanks alot, your proccess works great. I was just about to
>> give up
>> >> on the whole thing, so thanks again.
>> >>
>> >
>> > I'm glad that it worked for you.
>> >
>
>
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services,
> security?
> Get stuff done quickly with pre-integrated technology to make your
> job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache
> Geronimo
> http://sel.as-us.falkag.net/sel?
> cmd_______________________________________________
> Asunit-users mailing list
> Asu...@li...
> https://lists.sourceforge.net/lists/listinfo/asunit-users
>
>
|
Thanks for helping keep SourceForge clean.
X