Hi,
I am not aware of a case where Prism was used to develop a testing application, but if your testing application wouldn't benefit of any of the features provided withPrism, then it might not prove to be useful for it. Among the these features, the main advantages provided byPrism are:
- Separating the client-side application components in self contained and decoupledModules.
- Providing support for composing the application's UI in a decoupled fashion. (i.e. deciding the composition of theUI at run time and without needing the views to reference each other.)
- Built in support for dependency injections patterns as well as several communication capabilities between the components of the client-side application allowing them to work while being decoupled for each other.
If any of those features could be useful for your testing application, it could make sense to usePrism. However, I believe that those features do not have an impact in the testing logic part of the application. What's more, as far as I knowPrism does not include any specific guidance or capabilities to communicate withWeb Services or similar, so it wont provide any help regarding this topic either.
Regards,
Damian Cherubini
http://blogs.southworks.net/dcherubini