Evolving Web 2.0 apps
Do you have any suggestions on how to make Web 2.0 apps more reliable?

    Requires Free Membership to View

    Login

    When you register, you'll begin receiving targeted emails from my team of award-winning writers. Our goal is to keep you informed on recent service-oriented architecture (SOA) and SOA-related topics such as integration, governance, Web services, Cloud and more.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSOA.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSOA.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

I think emulation is key when evolving Web 2.0 apps, because the interdependencies in a relatively rich client side and service side environment make the validation process too complex to provide the desired coverage if you only test the full system. But when you emulate different parts, you will be able to better produce/reproduce error conditions and design use case scenarios that address the different states that can happen in a Web 2.0 environment. Then you can maintain these tests and emulations so you can replay and reuse as often as necessary whenever a part of the system changes.

This was first published in June 2008

Back to top