Comments on: Testing async services with Fluint http://saturnboy.com/2009/03/fluint-async-testing/ Code, Work, and Life Thu, 10 May 2012 17:13:39 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Valentin http://saturnboy.com/2009/03/fluint-async-testing/comment-page-1/#comment-16 Valentin Sun, 12 Apr 2009 14:56:36 +0000 http://saturnboy.com/?p=307#comment-16 thanks for pointing out wrong fluint swc, spent an hour trying to understand why flex can't find stupid TestResponder thanks for pointing out wrong fluint swc, spent an hour trying to understand why flex can’t find stupid TestResponder

]]> By: justin http://saturnboy.com/2009/03/fluint-async-testing/comment-page-1/#comment-13 justin Tue, 31 Mar 2009 04:22:35 +0000 http://saturnboy.com/?p=307#comment-13 Well, if you look at your Flex code through MVC glasses, I try to test everything in the Model with Fluint, including any async backend stuff. In the "pure" View, if a button doesn't show up or the Model is incorrectly rendered, it's really obvious and somewhat regression proof, so my View tests are typically sparse. To me, FlexMonkey is all about testing the Controller. I often have complicated Controller logic that makes button X bring up page Y or page Z depending on some data. This kind of stuff often shows regressions, so it's critical to cover it with FlexMonkey tests. Well, if you look at your Flex code through MVC glasses, I try to test everything in the Model with Fluint, including any async backend stuff.

In the “pure” View, if a button doesn’t show up or the Model is incorrectly rendered, it’s really obvious and somewhat regression proof, so my View tests are typically sparse.

To me, FlexMonkey is all about testing the Controller. I often have complicated Controller logic that makes button X bring up page Y or page Z depending on some data. This kind of stuff often shows regressions, so it’s critical to cover it with FlexMonkey tests.

]]> By: Justin Reidy http://saturnboy.com/2009/03/fluint-async-testing/comment-page-1/#comment-12 Justin Reidy Tue, 31 Mar 2009 00:54:19 +0000 http://saturnboy.com/?p=307#comment-12 I'm loving Fluint, but it can still be really tedious to write full UI integration tests with it. Is there a rule of thumb that you and/or Gorilla Logic use for deciding between FlexMonkey and Fluint? On an unrelated note, I discovered your blog through Juan Sanchez's link to your Degrafa button explorer, and I have to say that your content is spectacular. Please up the wonderful work! I’m loving Fluint, but it can still be really tedious to write full UI integration tests with it. Is there a rule of thumb that you and/or Gorilla Logic use for deciding between FlexMonkey and Fluint?

On an unrelated note, I discovered your blog through Juan Sanchez’s link to your Degrafa button explorer, and I have to say that your content is spectacular. Please up the wonderful work!

]]>