bvaughn / reflex-unit Goto Github PK

I think test runner needs to be made more in line with other test frameworks.

- Nested suites don't nest in the tree, so finding the right one will be
very painful if you have hundreds of tests

- Option to show only failed tests

- Increase view area of the stack trace, change font to monospaced and
increase font size

- Option to filter out reflex unit calls in the stack trace to remove
visual garbage

- Move the progress bar on top, stretch across and increase size for
greater visual impact

Problem:

It's a pretty commong thing to start tests right away with the test 
application. Currently there doesn't seem to be a way. 

Work around:

Dispatch a fake click:

runner.runAllButton.dispatchEvent(new MouseEvent(MouseEvent.CLICK));

Problem:

No classes is resolving under flexunit.framework.display.flexviewer.*

Solution:

Manually checkout the source.

What steps will reproduce the problem?
1. add the swc file to a actionscript or flex project using flex sdk (tested on 
version 3.0.1.1728
2. run the project


What is the expected output? What do you see instead?
The app is compiled but the sdk changed the method signature so it throws an 
error. If the swc is compiled with the new 
sdk it works fine.

What version of the product are you using? On what operating system?
tested on flex builder 3 on mac os x 10.5.3

Please provide any additional information below.

the debug stack trace:
ArgumentError: Error #1063: Argument count mismatch on 
mx.binding::PropertyWatcher(). Expected 3, got 2.
    at _reflexunit_framework_display_flexviewer_FlexViewerWatcherSetupUtil/setup()
    at reflexunit.framework.display.flexviewer::FlexViewer/initialize()
    at mx.core::UIComponent/http://www.adobe.com/2006/flex/mx/internal::childAdded()
    at mx.core::Container/http://www.adobe.com/2006/flex/mx/internal::childAdded()
    at mx.core::Container/addChildAt()
    at mx.core::Container/addChild()
    at mx.core::Container/createComponentFromDescriptor()
    at mx.core::Container/createComponentsFromDescriptors()
    at mx.core::Container/createChildren()
    at mx.core::UIComponent/initialize()
    at mx.core::Container/initialize()
    at mx.core::Application/initialize()
    at TestRunner/initialize()
    at mx.managers::SystemManager/http://www.adobe.com/2006/flex/mx/internal::childAdded()
    at mx.managers::SystemManager/initializeTopLevelWindow()
    at mx.managers::SystemManager/http://www.adobe.com/2006/flex/mx/internal::docFrameHandler()

1. Create and run a test method (i.e.
TestMethodExecution.testAllMetaDataMethodsExecuted)
2. Within the said test method, create and run another Runner with an
assertion that fails synchronously

An uncaught Flash Error is displayed (in the debug Flash player). This is
because the Wrapper for the first test method has not completed execution
of its method before the second test method failed.

I prefer "spec" notation for my test names:

public function should_return_correct_values() : void {}

Currently only "test" prefix is supported.

Workaround is to use [Test] metatag with -keep-as3-metadata+=Test compiler
option.

[Test]
public function should_return_correct_values() : void {}

Suggested fix:

Expose static array with prefixes.

assertEqual() should display both values when assertion fails.