Futurescale, Inc. PureMVC Home

The PureMVC Framework Code at the Speed of Thought

Over 10 years of community discussion and knowledge are maintained here as a read-only archive.

New discussions should be taken up in issues on the appropriate projects at https://github.com/PureMVC

Show Posts

* | |

  Show Posts
Pages: 1 ... 15 16 [17]
241  Announcements and General Discussion / Getting Started / Re: unit testing, how to start on: May 23, 2008, 09:32:41
We need a testing tool that works within the PureMVC app somehow. Like what Cactus does for testing in-container Java EE apps.

Perhaps a testing version of the framework where every actor pipes info about its actions to message queue which you then make assertions about the content of...


That sounds like a great idea. I'm interested in seeing the flow of data through the different stages of events to see potential problems where data is being changed incorrectly by something along the way (data leaves a proxy -> altered by a command -> altered again by mediator maybe -> rendered to visual component or lost along the way due to incorrect note name or type for example). My ideal testing would let me run a normal suite of unit test on things like components and proxies, and then a completely separate test afterwards that list the state of information as my app journey's through start-up and operation. Some sort of a tracing of information as I actually click test the app would be ideal.
242  Announcements and General Discussion / Getting Started / Re: unit testing, how to start on: May 23, 2008, 07:27:05
Wow, too funny. I came here today looking for the exact same question. I hope someone can give us a little guidance. As you say, testing individual functionality of components, proxies and commands is not difficult... but how to test the orchestration of the framework flow is another beast I can't even begin to understand where to start. I suppose for now I'll stick to testing the above mentioned areas, but hope someone can shed some light on testing the stability of things like start-up and shutdown of the app, event flow and user input.

My current project is quickly growing in size, up to about 300 files now and roughly 33,000 lines of code, and testing it's integrity is getting to be more and more important.
Pages: 1 ... 15 16 [17]