Fluint Discussions

As an update, when I run the sample application, I get the same error, but the build finishes with

Hey David, Im not sure if you are still looking for a solution to this but the flexunit4 in 360

Anyone else getting that error? I am trying to run 'ant package' and updated build.xml to

Thanks for the excellent testcase. I will review but this one is very difficult. Lack of global error

Yeah, I`ve noticed already such feature. My tests are asynchronous and asynchronous work is being

Figured this out. Had to manually Autowire the test class in the setUp method Swiz.autowire( this );

Hi all, it's me Jenis, remember me?). Jon finally marry me!! wedding was awesome! but my syster

Mike, Thanks so much for taking the time to respond to my post. I discovered the cause of the

To answer these questions: First, the async property actually causes this test to take a separate

I re-enabled moderation for all new users. I am not sure how it became disabled. Sorry if this slows

That is likely the best approach to accomplishing what you want On Sep 29, 12:53 pm, Jesse Warden

Figured it out finally... Being a long time Win32 dev, I know Flex and Java were case-sensitive

Tom, Can you attach (or email me) a patch file and I will review and apply. Thanks, Mike On Sep 17, 6

Tom, As you determined ITestSuiteModule is the correct interface. Will hunt down and destroy the

Mike, On Thu, Sep 10, 2009 at 04:18, Michael Labriola<malab...@gmail.com> wrote: > I

Michael, When you get there, I'd be glad to run it through our CI setup, if that helps (he says,

Yes. That did help. I don't know why I didn't realize I could take the guts from flex there

So, it seems that using the SDK that installs with Flex Builder fixes this issue. I was using a

Hi All, I have been trying to write a theory test for my component but doesnt seem to get it working,

Well, its not so much Fluint as a way to create it that it will work with Flex reliably. Honestly

I found the sources using svn checkout.

@conrad - Thanks for flushing this out. If you find out that this is a limitation of AIR, just let me

Also, just read the rest of your post. If the dataset is that large that your are comparing, you are

@debug Using assertThat(), throws(), and other matchers from hamcrest is another way to achieve fine

Overview of features and a link to some alpha bits: http://blogs.digitalprimates.net/codeSlinger/

Strictly speaking you should write two tests - one for textField1 and one for textField2. This is a

I would just like to say thank you. Yesterday we moved the client side of our project from flexunit

Hi, had the same issues. dpuint gave better output ;-) for now a solution just fix the output with

@Dan - Sounds like a great project. If you're interested in integrating fluint, let us know if we

Thanks for the great reply, Brian. It inspired me to change the Logon account for the Cruise services