In Siesta documentation I found :
- 1.Test the model first : You may already have heard the "fat model, skinny view" idiom. It means - put as much of business logic in the Model, don't pollute the View with it.
2.Test views (individual components) after Model
3.Test the application as a whole.
I have a lot of DataView in my project, and it has different behavior depending on data returned. This is also a business logic that must be on my View. Due this I am migrating my app but It looks like skinny model and fat view and controller(due GUI business logic), as events are controlled in controllers, I mean, all UI business logic. I realize some events is better treated in View component(object encapsulation), instead of using the controller to treat them, one example is DataView.
What I'am supposed to test in Models? Testing gets and sets it is in my opinion not necessary, since Sencha tested it, and it is supposed to work. I don' t want to test what is supposed to work and what have been tested by Sencha, for example, In forms the "allowBlank: false" is not tested by me.
It is great to test everything, even the Extjs framework to be sure everything is OK in all browsers, but now I am testing my logic and believing the framework works as expected. Does that make sense?
In my understanding the MVC pattern is different from server side and web client, due the nature of the UI.
Am I crazy in my thoughts?
I hope I use Siesta with CI server soon(and dont have CI yet ). Thanks for the excellent job! I am loving it!
Thks