http://research.microsoft.com/en-us/projects/ajaxview/

The Ajax View approach is to insert a server-side proxy (or web server plugin) in-between the web server machines and the end-user's browser. This proxy captures the web application's JavaScript code as it is being sent to a browser and rewrites the code to insert extra instrumentation code. The injected instrumentation code runs with the rest of the web application inside the end-user's browser and can capture performance, call graph, application state and user interaction information, providing visibility directly into the last hop of the user's experience.

Because Ajax View is rewriting web application code dynamically each time a user visits the web site, it can:

  • Serve different instrumentation code to different users. This allows us to distribute instrumentation code across many users, spreading the cost of gathering lots of information such that no single user pays a high performance penalty.
  • Adapt an instrumentation policy and serve different instrumentation code over time. For example, we can drill-down into performance problems and gather extra context about bugs.
  1. [2011/03/20] [Free] XStudio : Test management application *4 by vivekjog (3753)
  2. [2011/03/17] Application Testing Tool List *1 by Yohan Zetelberg (1359)
  3. [2011/03/11] How to Evaluate a Software Testing Tool by new2011 (1361)
  4. [2011/03/20] [Paid] QMetry : Software Test Management Tool by vivekjog (3993)
  5. [2011/03/21] Cong cu Quan ly cau hinh SVN *2 by STResearch (1136)