Just getting started, first post.
I've come across the patterns and practices labeled as Prism. Looks interesting.
I am trying to solve a test automation challenge at my work place. Currently there is not a quick and easy win with automation, it is an uphill battle fighting maintenance and speed to market challenges.
I want to solve this differently by creating an application which will simulate the various usages.
Here is my quest: I need to quickly build an application which will be used to test and verify lower level services. In our SOA platform, my application would sit virtually in the same space as other 'application' layers which consume
and run off of internal API's and provide a rich user experience to end users. However my applications purpose is to provide the coverage usage of all the possible variations that end users may put their application through. Rather than providing
a clean useful interface, my application should be suited to provide static cases we have defined and send to the underlying services and report back if the result was expected or not.
Thoughts on if Prism would be a good tool to use?
Other directions I am considering would be some cloud based application development for mobile applications -> quickest route to consume web services, rest/soap/wcf etc. Or possibly using a much more light weight language like ruby or something to quickly compose an application which really is doing little more than calling web services in certain logical order.
Thanks for lending a helping hand!