GUI Testing
Is your system performance issue at the client layer, network layer or the back end layer?
How long does it take to ‘render’ or execute the data once it has been delivered to the client end point – i.e. the point where your real users can read and interact with the interface?
How long does it take for my JavaScript to populate the system’s Combo drop down field with the data?
My current environment uses real physical desktops – what are the end user performance implications in delivering the Remedy client via a hosted virtual desktop (remote desktop) solution, such as: Microsoft Remote Desktop, Citrix XenApp, Citrix XenDesktop or VMware View client?
GUI testing, driving the test from the GUI, is used to expose any performance issues within the Remedy user tool or Remedy Web Page and gives the ultimate insight into the experience a real user will have when interacting with the Remedy system. This is because GUI driven testing, by definition, includes the client side rendering of the final presentation layer to the user and application processing execution times which could highlight, for example, that there is a poorly performing JavaScript component involved in manipulating and transforming the data returned from a query, or other similar issues.
Scope: An automated script, written by Scapa Technologies professional services, drives the Remedy Client application for one workflow (additional workflows can be purchased) and is run at the same time as other protocol (C API and mid-tier) driven tests.
Outcome: The Scapa Technologies professional services report will provide an understanding of the system performance information with particular reference to the response times experienced by your system users.
