road0001 / as3flexunitlib Goto Github PK

Current TestSuite.addTest does not work properly.  If you pass in a test
instance, none of the methods will be loaded.

The attached patch (with unit tests, naturally) fixes this issue.

Hello. I'm at a loss about the behavior of == operator.
1. assertEquals({}, {}) => AssertionFailedError
2. assertEquals([], []) => AssertionFailedError

I think a assertEquals method should use ObjectUtil.compare() for comparison.
This method compares objects recursively.

I've made some modifications to build.properties to allow the SDK path to
be specified in one place.

In addition, I suggest the build process use the compiled flexunit library
rather than specify a second copy.  That allows the user to type "ant test"
and have it compile and test.

currently it only proxies callbacks with one parameter. 

Would be nice it could track any asynchronous callbacks.

The following changes seem to work for me:

in the AsyncTestHelper.runNext()

use this code:

          if (extraData != null)
            {
                //func(objToPass, extraData);
                objToPass.push(extraData);
                func.apply(testCase, objToPass);
            }
            else
            {
                func.apply(testCase, objToPass);
            }
            func = null;
            objToPass = null;
            extraData = null;
        }

update the handleEvent() signature to:

  public function handleEvent(...event) : void

And they seem to do the trick. 

What steps will reproduce the problem?
1. Look at FlexUnit v.85 ASDocs
2. Look at source for TestCase and TestSuite
3. ASDoc docs don't show up in ASDocs

I've posted a fix on my blog:

http://www.brightworks.com/flex_ability/?p=28 

I configured a builder(adl.exe test-app.xml) that gets run after auto
project build.

If there are errors or failures during the test the window with test
results is closed. But to get the number or errors and failures I have to
parse the labels, which looks like a hack.

We wanted the ability to run trace statements from our tests without having
to actually run the debugger, so I've made some modifications to the flex
unit source.  This patch adds the following:

1)  Adds 5 new utility methods to TestCase:  info(), warn(), debug(),
error() and fatal().
2)  Adds a new tab to TestRunnerBase for viewing output generated by
calling methods above.
3)  Updates build.xml to use Flex Builder 3 install folder instead of Flex
Builder 2.

Hello,

I'm wondering if what I'm getting is a correct behaviour in my case:

1. I'm populating an object like this:
obj.attr = xml.@attr;

2. I'm testing it like:
assertEquals(xml.@attr, obj.attr);

3. When the there was no attribute "attr" in the XML node I get:
Error: expected:<> but was:<>

Is that correct behaviour?


Thanks and best regards,
Cyprian

http://as3flexunitlib.googlecode.com/svn/trunk/src

and

http://as3flexunitlib.googlecode.com/svn/trunk/src/src

are identical.  The second directory should be removed from the source tree.

What steps will reproduce the problem?
1. Run the test runner. 
2.
3.

What is the expected output? What do you see instead?
Expecting the error and the stack trace.
i get the error caught test fails bt no stacktrace

What version of the product are you using? On what operating system?
0.85

Please provide any additional information below.

What steps will reproduce the problem?
1. Setup an async test using addAsync

If the async event fires before the completion of the code in the 
runMiddle method, all hell breaks loose.

What is the expected output? What do you see instead?
addAsync would work regardless of timing of the asyncEvent

What version of the product are you using? On what operating system?
Latest on XP

Please provide any additional information below.
I have a fix for this plus the ability to do asynchronous startup. Let me 
know if you are interested in reviewing the code.

Mike Labriola

What steps will reproduce the problem?
1. Download FlexUnit from Google Code
2. Unzip with WinZip on Windows fails - indicates not a valid archive
3.

What is the expected output? What do you see instead?
Expected to be able to unzip the download

What version of the product are you using? On what operating system?
WinZip 81. on Windows 2000 SP2

Please provide any additional information below.

What steps will reproduce the problem?
Just run the following testcase:

public function testMultipleCallsOfAddAsync(): void {
     var dispacher:EventDispatcher = new EventDispatcher

     dispacher.addEventListener("MySecondEvent", this.addAsync(function (event:Event):void  {
        assertEquals("The function supposed be called on MySecondEvent", "MySecondEvent", 
event.type)
     }, 3000))

     dispacher.addEventListener("MyFirstEvent", this.addAsync(function (event:Event):void  {
        assertEquals("The function supposed to be called on MyFirstEvent", "MyFirstEvent", 
event.type)
     }, 3000))

     var timer: Timer = (new Timer(1000))
     timer.addEventListener(TimerEvent.TIMER, function (event:*):void {
        // dispach async event in reverse order.
        dispacher.dispatchEvent(new Event("MyFirstEvent"))
        dispacher.dispatchEvent(new Event("MySecondEvent"))
        timer.stop()
     });
     timer.start()
}



What is the expected output? What do you see instead?

The expected output is successful run of both test cases.
Unfortunately flexunit seams to execute both function on the first
event.


What version of the product are you using? On what operating system?
flexunit-.85, Mac OS X 10.5

Please provide any additional information below.

What steps will reproduce the problem?
1. use addAsync in a setUp function of a test

What is the expected output? What do you see instead?
If a test fails after the setUp method flexunit doesn't catch the failure,
instead an error is thrown.

What version of the product are you using? On what operating system?
flexunit-.85 on Windows.

What steps will reproduce the problem?
1. Set up a test suite 
2. Run in debug mode
3. On encountering exception, exception shown in TestRunnerBase

What is the expected output? What do you see instead?
I see what is expected. However when im running in debug, i'd like to 
catch the exception in the Flex debugger and not TestRunnerBase. So far, 
I've explicitly encountered this issue with null reference assignments.

What version of the product are you using? On what operating system?
.85 - WinXp

Please provide any additional information below.
An option to not catch all exceptions would suffice.
I use the unit tests to test my code well before I have any other 
mechanism for using it. When the Runner catches the exception and shows 
it, it robs me of my ability to see the state of the app and to have the 
line where the problem occured highlighted.

Most ant scripts have a "clean" task.  This allows rapid iteration of
development, compiling, and testing.  Here's a simple one to add to the end
of build.xml

    <target
       name="clean"
       description="deletes the bin directory and other temporary files"  >

       <delete includeEmptyDirs="true" failonerror="false">
            <fileset dir="${bin.dir}" />
       </delete>

     </target>  

What steps will reproduce the problem?
1. We have a test project that has linked in the build path the src folder
of other two projects (the main project and the core library).
2. We created in the core library project our own Logger that it is used in
the main project.
3. When we run the tests, the Logger inside the main project classes is null
4. If we modify the logger (changing its name, or changing method names) it
works the very first times, then we are back again with the issue.

What is the expected output? What do you see instead?

I would expect that the Logger is always available since it has been
imported. We tried also forcing its importing (adding it also when not
needed and using it with its full namespace), no luck.


What version of the product are you using? On what operating system?

Flex 2.0.1 eclipse plugin in Windows  and FlexUint .85 

Please provide any additional information below.

We tried many options, but still in the dark.

Create an ANT build script (in /trunk/build/build.xml) with "doc",
and "lib" targets to make it easy for people to generate the latest
documentation and .swc binary from the source.

What steps will reproduce the problem?
1. create TestSuite called AllTests
2. create TestSuite called CollectionsTestSuite
3. add CollectionsTestSuite to the AllTests TestSuite using the
addTestSuite( CollectionsTestSuite ) method
4. run tests

What is the expected output? What do you see instead?

I expect the tests of the CollectionsTestSuite to run.
Instead a null point is thrown in TestSuite.addTestMethods()


What version of the product are you using? On what operating system?

0.85 Mac OS

Please provide any additional information below.

the src for the test project I used is attached.
I presume that FlexUnit should have this functionality, as JUnit has it and
it is a basic requirement in my opinion? 

The current build file fails when the paths contain spaces (due to lack of
quotes).  Here's a patch to fix it.