This slide gives an overview of the key areas (core Application Lifecycle) that need to be addressedThe integrations and traceability between this key areas is key to ensuring management, visibility and quality into the application lifecycle.Addressing the key personas involved in the application lifecycle on one single, collaborative solution:Business AnalystsProject TeamsDevelopment TeamsQA Teams
This slide gives an overview of the key areas (core Application Lifecycle) that need to be addressedThe integrations and traceability between this key areas is key to ensuring management, visibility and quality into the application lifecycle.Addressing the key personas involved in the application lifecycle on one single, collaborative solution:Business AnalystsProject TeamsDevelopment TeamsQA Teams
Тестовое покрытие не полноRUMскриптыПрофиль нагрузочного теста не похож на продуктивныйRUMтранзакцииЗаглушки «нереально» производительныSVВоздействие слабых сетей не изученоShunra
HP Service Virtualization is software for simulating functional and performance behavior of otherwise unavailable application components.Instead of applications hitting these systems, SV allows IT Dev and Test to eliminate dependencies on unavailable or inaccessible components and services by creating virtual versions for testing. It allows dev teams to speed up application development as it can simulate service components during the build phaseAnd it allows teams to use SV to begin to learn and simulate application behavior and begin testing against these simulated virtual services earlier, find problems earlier, and save orgs time and money.
Todd to JohnThis is a screenshot from LoadRunner with a test scenario running.The scenario has 500 VUsers running as local (way most customers are falsely testing today) and then begins to introduce 50 emulated mobile VUsers.From the results we can see that with only 9 mobile VUsers (or 1.8% of the overall VUser population) transaction response time (TRT) goes from ~1 second to ~5 seconds for ALL VUsers.This illustrates the significant impact that mobile users have on performance (and Functionality), both from an ‘end user’ and ‘backend infrastructure’ perspective.Without Shunra, this would have gone un-notice until production, where it very easily could have taken down the production site / app for ALL users.
John
John to ToddIMPORTANT: ~70% of the end-to-end performance of a mobile app is a result of the network. As a result, without using Shunra, you will get ‘false positives’ resulting in significant risk of failure in production. This risk is both ‘Front End’ and ‘Back End’ and will impact ALL of your users.Mobile applications and the mobile network create unique performance challenges on several levels:First – The performance of a mobile device will dramatically vary depending on the quality of it’s network signal. In most cases, on a mobile network, the majority of transaction time will be consumed in the mobile network and will not be on the device or back end servers. Second – Mobile devices and mobile connections require more back end resources to support them. They open connections to servers and take much longer to complete transactions. The addition of a few mobile clients to an existing system can have a dramatic impact on the performance of the whole system, not just the mobile users.In order to minimize the risks associated with mobile performance, HP’s industry leading LoadRunner and Performance Center tools are able to record and execute mobile performance tests. Supporting both browser applications and native applications, customers are able to script and test their mobile applications. The network is a very real challenge, and ensuring that changing and realistic network conditions are incorporated in the testing process is where our partner Shunra enters the equation. With their integrated Shunra for HP product, load tests can support dynamic and realistic network conditions to ensure that the performance test is accurate and reliable.
Information about window’s size, position, docking, state (opened or hidden) is saved under the current layout name
Introduces a new way to get a visual context of the script while reviewing its code. It provides a new way to navigate to a location in the code using a visual representation of the business process.
Key FeaturesCommon look and feel of all the snapshots within the Snapshot View.Split view synchronization.Brand new snapshot content displayed for most step types (i.e. Xml Viewer, Buffer Viewer, Image Viewer, revised HTTP Viewer, etc…).
Key FeaturesSearch per Script or ActionStep context menuThumbnail viewSync with other panes
Major enhancements:Code completion list Syntax highlight for the C codeHighlighting of the Step parametersCollapsing of user-defined functionsTooltips display information for user-defined functions, parameters, etc.
Breakpoint pane - displays the list of breakpoints in all opened actionsCallback - contains the list of stack frames according to the current debugger source positionWatch - manages user defined watch expressions
APIsLoadRunner 11.50:web_reg_save_param_ex()Enhanced web_reg_save_param()Smart scoping for formatted data (DFE)web_reg_save_param_XPath()Correlate by XPathweb_reg_save_param_regexp()Correlate by Regular expression (Perl syntax standards)Record based correlationsReplay based correlationsCorrelation rulesCorrelation from snapshot