Mock Spark component

[NagRock]

Hi, when I want to prepare mock for spark component it takes really long time... And when i turn on coverage plugin... tests takes GB of ram and never ends...

[Hob Spillane]

Mocking of view components takes a very long time. Your best option is to create an interface for your view so that you can mock the interface instead.

[Drew Bourne]

Perfect answer Hob. 

Anything deriving from UIComponent will take a long time to generate the proxy as it has hundreds of methods and accessors. And this happens for each separate UIComponent-subclass that you give to Mockolate. 

I am considering a feature to allow specifying which methods should be proxied, however even if this feature was available now I would strongly suggest using interfaces instead. Consider using IUIComponent or IVisualElement, or something custom depending on your requirements. 

cheers, 

Drew

[NagRock]

Thanks, sounds great. Gona check it :)

[NagRock]

Hi, but when I want to mock for example spark DataGrid i have only: IFocusManagerComponent, IIMESupport for that component.

So I don't have interface for it.

I wanto to check if dataProvider setter was called.

[Hob Spillane]

In those cases, what I'll typically do is create a new interface that defines only the methods I need to interact with, then implement that method myself on a sub-class of the view I'm trying to mock.

[Stray]

+1 for this method.

[NagRock]

Thanks again. You really helped me :)

[Theo]

When testing mediators I need to mock their views. What I often do is create a partial mock, it doesn't take long and will still dispatch events (something that I often need my views to do), however you can still mock all the calls you want and set exceptions etc. 

Theo.