DOCSLIB.ORG

Load Testing Fundamentals

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Load Testing Fundamentals Load testing fundamentals Colin LEVERGER, E.N.S.S.A.T. LANNION [email protected] his paper will provide an overview of users can be simulated by computers to browse ser- one of the main test specialties, known vices and to follow classical user paths. The goal is Tas the load testing. It will give a pre- to observe the behavior of the servers under this ar- view of the methodologies and tools used by tificial generated load, and to ensure that the service professionals of this domain. will not shut down under any circumstances. There are several ways to test a system. Seven of the mains will be listed below [Smar]. 1 Introduction 1. Unitary Test: validation of all functional aspects Load testing is becoming a major preoccupation for of the website (∼ 5 mins) big companies, since the huge expansion of the web and the evolution of uses. Everyone wants to be 2. Component Test: validation of precise con- connected at any time, to use the internet for various text/use cases (∼ 25 mins). reasons (buy, sell, communicate. ). As a company, it is important to maintain a high quality of service 3. Capacity Test: search of the limits of the system, if you do not want to lose any client. A recent report in terms of the number of simultaneous users, says that 40% of shoppers abandon a website that network use, etc. (few hours). takes more than 3 seconds to load [Kiss]. Even more 4. Soak Test: validation of performance during important, a one second page delay in a website very long lapse of time (from 4 to +12 hours). making $100,000 a day could potentially cost $2.5 million in lost sales every year [Kiss]. 5. Stress regime Test: validation of websites with The load testing field represents all the methods several load peaks in a relatively short lapse of used to benchmark a website/software. The goal is time (few hours). to be sure that it will work properly under a high load (with a lot of people browsing the service at the 6. Redundancy Test: validation of load reparti- same time). tion between several equipment (from 2 to +12 We will discuss here about context, methods and hours). tools used to do a load test. 7. Fail-over Test: validation of service behaviors in case of crashes (from 2 to +12 hours). 2 What is load testing? Note that the tests listed above have to be exe- When we talk about load testing, we talk about meth- cuted in theory in this exact order. Indeed, if the ods to simulate load on a service/website. Virtual Unitary Tests are not validated, it is not wise to Page 1 of4 go ahead|you should probably adapt your product 4 Tools before continuing. There are plenty of tools to execute load tests, and choosing one could be difficult. There are some points 3 Methodology Followed by Load to considerate before making a choice: Testers • Budgets given to test team, There are quite a few steps before the tests execution • Prices of tools, themselves. Most of the time, in big companies, the need is written in a specification paper, given by • Number of virtual users to simulate, the project's owners. This one can be very precise, or not: anyway, it should be before starting the • Centralized/decentralized architecture, realization because it will be the guideline during the • Duration of the test campaign, entire process. If it is not precise enough, the tester himself should imagine practical solutions to test the • Special needs for tests. considered system, by developing the given drafts. When the specifications are clarified, it is time to 4.1 Features of tools think about the test platform. As a matter of fact, it is forbidden to execute tests on the production The tools used by load testers are basically simulat- platform, because there are big chances to break ing load on servers. It is possible to program tests, the service (and to lose clients!). The test platform configure details, and to launch the virtual users will be an exact replica of the production platform browsing with them. (machines, infrastructure, filer. ). The market of load testing tools is huge, and plenty Then, it is important to choose and install the of products are available. Most of them offer basic right adapted tools. To learn more about tools, see features, such as the possibility to choose the num- section4. ber of virtual users to simulate, to give a target of After all these previous preparation steps, the tests several different servers, to code different paths for should now begin. In this part, it is important to authorized/unauthorized users, to monitor the test follow the guidelines defined in the first step. These and create graphs. Almost every load testing tool guidelines could contain: allows to use injectors; the injectors are separated machines which are slaves of the main test computer. • Use cases, They are used to simulate more virtual users. In- deed, load testing is consuming a lot of memory and • User paths to follow, we often need more than 50 machines to simulate thousands of users1. • Credentials, In another hand, some products offer exotic fea- tures. It can be possible to watch answers time for • Details about sensible application parts. specific language (Java, PHP, . ), to chain different tests together, etc. Theses features are sometime The tester should be aware of all these details, offered by free and open source projects, but most execute the tests and store results to analyze them of the time, if the need is very specific, it could be carefully. Of course, the final step of the test cam- found on expensive solutions. paign consists in writing a report, which will explain Some projects are using different tools for the same the problem(s) found on the application, the proce- tests campaign, but it is definitely better to try to dure followed during tests to the client and the rec- fit all the needs with only one product. ommendations to improve the production platform performances according to the clients' use. This doc- 4.2 Record the test scenarios ument is critical, because it will be the entry point to improve the application. Scenarios have to be recorded in order to replay Note that the entire process described above is them with thousands of virtual users. To do so, the iterative, and could be executed more than once for 1For example, with a computer with only 8 gigs of memory, a more complex campaign. It is still a good habit to it is barely possible to simulate 100 virtual users before improve the quality of the tests iteratively. having a problem on the computer. Page 2 of4 tools chosen will in most of the cases be used as a • Gatling is not distributed; it is possible to lunch proxy through which all the requests will pass and multiple Gatling on different hosts but it is fully be analyzed. manual. In other words, no injectors on Gatling! A typical scenario will be a user path; this user can do actions such authentification, page browsing, • Gatling is totally asynchronous when JMeter is etc. All the actions done by this particular user will synchronous. For JMeter, the paradigm One be recorded, with the exact tempo included. user = one thread is applied, which is not the It is possible to record as many scenarios as there case with Gatling. is user paths. It is then possible to assign a certain • Gatling produces a fancy report at the end number of users to a specific scenario, with a bunch of every test, and this dynamic report (full of of possible customizations. HTML/JavaScript) is easy to read. JMeter only produces graphs (note that it could be possible 4.3 Open Source to find a module for that but it is not native). The main benefit in using an Open Source product is that it is often totally costless. The high community 4.3.3 What about cloud solutions? around this kind of product is usually reliable, and it can be a good help if there are problems with the The two solutions cited above are software that software. should be installed on physical machines. We are I will now introduce some of the greatest free and living on a Cloud era, and a lot of people have un- open source load testing tools. derstood that it is interesting to have access to load testing functionalities on demand via a web service. Most of the Cloud solutions are based on JMeter; 4.3.1 JMeter they are just simplifying the process of installing First, one of the worldwide most used tools is JMeter. injectors, configuring JMeter by providing beautiful This tool is a pure java application designed to load web interfaces. Most of theses solutions are commer- test functional behavior and measure performance. It cial. was originally designed for testing Web Applications We can mention BlazeMeter or Octoperf which but has since expanded to other test functions [Apac]. are ambassadors of this kind of solution. JMeter is able to test a lot of different servers/protocol types, is multi-threaded, and has a 4.4 Commercial Applications java GUI which facilitates the configuration of the tests and is highly extensible. Indeed, it is possible The use of commercial solutions is sometimes com- to enrich it with modules, developed by you or by the pulsory, because these solutions are often proposing community. JMeter is distributed, which means that a lot more parameters than open source solutions. it can be used with multiple injectors.
Load more

Recommended publications
  • Hardware & Software Standards
    Hardware & Software Standards Introduction This document identifies the current City of Chicago standards for its hardware and software environments, and is intended primarily for City department and vendor use. These standards do not mean that other software and hardware, which might have been previously listed as standard, may not be used or supported, but the following items should be purchased for any new initiative or growth/replacement needs. Any proposals for non-standard hardware or software purchases or questions/comments should be forwarded to the Department of Innovation and Technology (DoIT) Enterprise Architecture Board for review, and will need to be approved via the Technology Purchase Review and Approval (TPRA) process. Standards denoted with an asterisk (*) are currently under review. Platform Standards Operating System (O/S) Hardware Platform Solaris 10 (Unix) (Oracle) Sun Microsystems RedHat Linux Enterprise Server 6.x, 7.x Dell RedHat Linux Enterprise Server 7.x (PCI Services) Dell VMWare VSphere 6.5U1 Dell Windows 2012 R2 & 2016 (Standard and Enterprise) Dell Windows 7, Windows 10 Dell, Panasonic Page 1 of 6 Last Revised January 2018 Hardware & Software Standards Enterprise Services Type Windows 2008 Server All other platforms Oracle Enterprise 11gR2, 12cR1; Postgres 9.x or 10.x (EnterpriseDB or Database N/A community) Print O/S n/a File O/S n/a Email Exchange 2016 / Office365 n/a Desktops, Laptops, & Tablets Type Model Standard Users Dell OptiPlex 5050 SFF, Dell OptiPlex 7450 All-In-One Mobile User Latitude 12 Rugged Extreme Latitude 14 Rugged 5414 Latitude 12 2 in 1 with case and Doc Latitude 5480 14" Laptop 6th gen proc High-End Workstation Dell Precision T5810 Laptop Accessories Docking- For the E-5470 units, Dell Business Dock - WD15 with 130W Adapter Monitor Dell 23 Monitor – P2317H Page 2 of 6 Last Revised January 2018 Hardware & Software Standards Printing and Scanning The Department of Fleet and Facility Management (2FM) oversees print services for the City of Chicago.
    [Show full text]
  • IT CLASSIFICATION TECHNOLOGY LIST – ISSUE DATE: April 18, 2017
    IT CLASSIFICATION TECHNOLOGY LIST – ISSUE DATE: April 18, 2017 Technology Definition: A set of knowledge, skills and/or abilities, taking a significant time (e.g. 6 months) to learn, and applicable to the defined classification specification assigned. Example of Tools: These are examples only for illustration purposes and are not meant to constitute a full and/or comprehensive list. CLASSIFICATION DISCIPLINE TECHNOLOGY DEFINITION EXAMPLE OF TOOLS Omegamon, IBM Admin Tools, Log Analyzer, Relational The relational database management system provided by IBM that runs on Unix, Linux, DBA DB2 DB2 Compare, Nsynch, TSM, Universal Database Windows and z/OS platforms including DB2 Connect and related tools. Command, SQL SQL Server Mgmt. Studio, Red Gate, Vantage, SQL Server The relational database management system and related tools provided by Microsoft Corp. Tivoli, Snap Manager, Toad, Enterprise Manager, SQL ORACLE The relational database management system and related tools provided by Oracle Corp. ASE SYBASE The relational database management system and related tools provided by Sybase. Cincom SUPRA SQL – Cincom’s relational database management system provides access to data Supra 2.X in open and proprietary environments through industry-standard SQL for standalone and client/server application solutions. Open Source Open Source database management system such as Mysql. Phpadmin, mysqladmin, Vertica Hierarchical The hierarchical database management system provided by IBM that runs on z/OS mainframe IMS BMC IMS Utilities, Strobe, Omegamon Database platform including related tools. Cincom SUPRA® PDM – Cincom’s networked, hierarchical database management system provides access to your data through a Physical Data Manager (PDM) that manages the data Supra 1 structures of the physical files that store the data.
    [Show full text]
  • Kickstart Your Gatling Performance Testing
    Kickstart Your Gatling Performance Testing Siegfried Goeschl Version 1.0.0, 2018-11-04 Introduction 1 Siegfried Goeschl • Senior Software Engineer • Writing server-side code • Java Meetup Vienna co-organizer • Apache Software Foundation member • Currently working at Erste Bank Austria 2 Introducing Gatling • Performance testing framework • Tests are written in in Scala • Developer-centric test tool • Development started in 2010 • Gatling 3.0.1 released now • Since V3 there are two license models - free & commercial. • As you know some guys have a strong opinion about OSS 3 What Linus Says 4 5 • Having said that a commercial license could generate more revenue keeping the Open Source version alive. 6 Money Makes The World Go Round 7 Gatling vs. FrontLine • Gatling Open Source is under ASL 2.0 • Gatling FrontLine is the enterprise edition ◦ Annual license or "pay as you go" ◦ Web-based, ◦ More bells & whistle ◦ Real-time reporting 8 Under The Hood • Supports HTTP 1.1/2.0 & JMS protocol • Response validation ◦ Regular expressions ◦ XPath & JSONPath ◦ CSS selectors 9 Under The Hood • Provides Domain Specific Language (DSL) • Uses asynchronous non-blocking HTTP client • Integrates with Maven, SBT & Gradle • Test data feeders CSV, JSON, JDBC, Redis • Management-friendly HTML reports • No more 1:1 mapping between virtual users and worker threads. 10 When To Use Gatling? • Want to write test code in your IDE? • Need some integration & performance tests? • Want to run those test on your CI server? • Do you care about reviews and version control? 11 Getting Started 12 Getting Started • JDK 1.8 • Apache Maven 3.5.x • IntelliJ Community Edition • IntelliJ Scala Plugin 13 Getting Started • https://github.com/gatling/gatling-maven-plugin-demo • Import the Maven project into your IDE • Write and debug Scala code there • Execute Gatling tests on the command line • Simple CI integration using Maven • The official Gatling distributable is not suited for development.
    [Show full text]
  • Tero Suominen PERFORMANCE TESTING REST APIS Information
    Tero Suominen PERFORMANCE TESTING REST APIS Information Technology 2017 PERFORMANCE TESTING REST APIS Suominen, Tero Satakunta University of Applied Sciences Degree Programme in Computer Science December 2017 Number of pages: 39 Appendices: 0 Keywords: REST, performance testing, automation ____________________________________________________________________ The subject for this thesis was performance testing REST APIs that had been imple- mented into a Java application. The purpose of this research was to come up with a method on how the performance and functionality of the REST APIs could be meas- ured and tested within Profit Software. The research consisted of two parts. First, I searched to find an existing software ca- pable of being used for testing REST APIs. After selecting the tool that would be used to create the performance tests, a local test environment was set up that allowed us to estimate the capability of the software and the method of testing itself. The local envi- ronment consisted of the same components and software that could be used also in the already existing test environments within the company. This way moving the tests from the local environment into the actual test environment went smoothly. With the help of this research we were able to detect issues with the functionality of some APIs, when they were under load. We were able to fix these issues in the imple- mentation during the development phase and after changing the implementation we could verify that the APIs functioned correctly by using these same tests. REST RAJAPINTOJEN SUORITUSKYKYTESTAUS Suominen, Tero Satakunnan ammattikorkeakoulu Tietotekniikan koulutusohjelma Joulukuu 2017 Sivumäärä: 39 Liitteitä: 0 Asiasanat: REST, suorituskykytestaus, automaatio ____________________________________________________________________ Opinnäytetyön aiheena oli Java-sovellukseen toteutettujen REST rajapintojen performanssitestaus.
    [Show full text]
  • Enterprise Development with Flex
    Enterprise Development with Flex Enterprise Development with Flex Yakov Fain, Victor Rasputnis, and Anatole Tartakovsky Beijing • Cambridge • Farnham • Köln • Sebastopol • Taipei • Tokyo Enterprise Development with Flex by Yakov Fain, Victor Rasputnis, and Anatole Tartakovsky Copyright © 2010 Yakov Fain, Victor Rasputnis, and Anatole Tartakovsky.. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://my.safaribooksonline.com). For more information, contact our corporate/institutional sales department: (800) 998-9938 or [email protected]. Editor: Mary E. Treseler Indexer: Ellen Troutman Development Editor: Linda Laflamme Cover Designer: Karen Montgomery Production Editor: Adam Zaremba Interior Designer: David Futato Copyeditor: Nancy Kotary Illustrator: Robert Romano Proofreader: Sada Preisch Printing History: March 2010: First Edition. Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly Media, Inc. Enterprise Development with Flex, the image of red-crested wood-quails, and related trade dress are trademarks of O’Reilly Media, Inc. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O’Reilly Media, Inc. was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this book, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information con- tained herein.
    [Show full text]
  • Web-Engineering" Kapitel 9: Website-Analyse Und -Optimierung
    Reader zum MOOC "Web-Engineering" Kapitel 9: Website-Analyse und -Optimierung Die PDF-Datei wurde mit Hilfe des Open-Source-Werkzeugs „mwlib“ erstellt. Für weitere Informationen siehe http://code.pediapress.com/ PDF generated at: Sat, 14 Dec 2013 16:53:28 UTC Inhalt Artikel Web-Controlling 1 Web Analytics 1 Google Analytics 7 Piwik 10 AWStats 12 Webalizer 14 Logdateianalyse 16 Ganglinie 20 Konversion (Marketing) 22 Conversion-Tracking 24 Click-Through-Rate 25 Besucherzähler 26 Unique Visit 27 Referrer 28 Seitenabruf 30 Zählpixel 32 Cron 34 Do Not Track 38 Web-Monitoring 41 Munin (Software) 41 WPO: Web Performance Optimization 44 Google Page Speed 44 SPDY 45 Performnace-Test 47 Lasttest (Computer) 47 Stresstest 50 Apache JMeter 52 Dienstgütevereinbarung für Websites 53 Service-Level-Agreement 53 Webhosting 55 SMART (Projektmanagement) 58 Downtime 59 Verfügbarkeit 60 Paketumlaufzeit 62 Quellennachweise Quelle(n) und Bearbeiter des/der Artikel(s) 64 Quelle(n), Lizenz(en) und Autor(en) des Bildes 66 Artikellizenzen Lizenz 67 1 Web-Controlling Web Analytics Web Analytics (auch Web-Controlling, Web-Analyse, Datenverkehrsanalyse, Traffic-Analyse, Clickstream-Analyse, Webtracking) ist die Sammlung und Auswertung des Verhaltens von Besuchern auf Websites. Ein Analytic-Tool untersucht typischerweise, woher die Besucher kommen, welche Bereiche auf einer Internetseite aufgesucht werden und wie oft und wie lange welche Unterseiten und Kategorien angesehen werden. In Deutschland ist der Einsatz solcher Werkzeuge aus Datenschutzgründen umstritten. Sie wird vor allem zur Optimierung der Website und zur besseren Erreichung von Zielen der Website (z. B. Häufigkeit von Besuchen, Vermehrung von Seitenaufrufen, Bestellungen, Newsletter-Abonnements) eingesetzt. Grundlegend kann bei Web Analytics zwischen Auswertungsverfahren zur permanenten Messung der Site-Effektivität und Methoden zur Auffindung von Schwachpunkten in der Site und Verbesserungsmöglichkeiten unterschieden werden (siehe Methoden).
    [Show full text]
  • Loadrunner Professional and Loadrunner Enterprise 2021
    Product Flyer Application Delivery Management LoadRunner Professional and LoadRunner Enterprise 2021 License Bundles Community bundles and license bundles available for LoadRunner Professional and LoadRunner Enterprise 2021. Learn more at Community Bundles (Free of Charge) https://software.microfocus.com/ Bundle Name Description products Community 50 Vusers for all protocols, except for Templates and GUI Mobile UI Unlimited Vusers for the TruClient—Native Mobile protocol. Note: This bundle requires an Micro Focus Mobile Center license. For more details, see: https://software.microfocus.com/software/customer-technical-support-services License Bundles Bundle Name Protocols .NET Record/Replay Microsoft .NET Database ODBC Oracle—2 Tier Development SDK Unit Test—NUnit, Junit Selenium, LeanFT* GUI Unified Functional Testing (UFT) Java Java Record Replay Java over HTTP Mobile and IoT DevWeb JMeter Gatling Web—HTTP/HTML TruClient—Mobile Web SMP (SAP Mobile Platform) MQTT (Internet of Things) CoAP (Internet of Things) Network DNS (Domain Name Resolution) FTP (File Transfer Protocol) IMAP (Internet Message Access Protocol) LDAP (Listing Directory Service) MAPI (Microsoft Exchange) POP3 (Post Office Protocol) SMTP (Simple Mail Transfer Protocol) Tuxedo Windows Sockets (Winsock) Oracle E-Business DevWeb JMeter Gatling Oracle NCA Oracle—Web Siebel—Web Web—HTTP/HTML * Continued on next page LeanFT support is for LoadRunner Enterprise only. Contact us at: www.microfocus.com Like what you read? Share it. Bundle Name Protocols Remote Access Citrix ICA
    [Show full text]
  • Continuous Quality and Testing to Accelerate Application Development
    Continuous Quality and Testing to Accelerate Application Development How to assess your current testing maturity level and practice continuous testing for DevOps Continuous Quality and Testing to Accelerate Application Development // 1 Table of Contents 03 Introduction 04 Why Is Continuous Quality and Testing Maturity Important to DevOps? 05 Continuous Testing Engineers Quality into DevOps 07 Best Practices for Well- Engineered Continuous Testing 08 Continuous Testing Maturity Levels Level 1: Chaos Level 2: Continuous Integration Level 3: Continuous Flow Level 4: Continuous Feedback Level 5: Continuous Improvement 12 Continuous Testing Maturity Assessment 13 How to Get Started with DevOps Testing? 14 Continuous Testing in the Cloud Choosing the right tools for Continuous Testing On-demand Development and Testing Environments with Infrastructure as Code The Right Tests at the Right Time 20 Get Started 20 Conclusion 21 About AWS Marketplace and DevOps Institute 21 Contributors Introduction A successful DevOps implementation reduces the bottlenecks related to testing. These bottlenecks include finding and setting up test environments, test configurations, and test results implementation. These issues are not industry specific. They can be experienced in manufacturing, service businesses, and governments alike. They can be reduced by having a thorough understanding and a disciplined, mature implementation of Continuous Testing and related recommended engineering practices. The best place to start addressing these challenges is having a good understanding of what Continuous Testing is. Marc Hornbeek, the author of Engineering DevOps, describes it as: “A quality assessment strategy in which most tests are automated and integrated as a core and essential part of DevOps. Continuous Testing is much more than simply ‘automating tests.’” In this whitepaper, we’ll address the best practices you can adopt for implementing Continuous Quality and Testing on the AWS Cloud environment in the context of the DevOps model.
    [Show full text]
  • Roman Udka Software Test Automation Engineer
    Roman Udka Software Test Automation Engineer Location: Ukraine, Kharkiv Telegram/Cell phone: +380994365885 E-Mail: [email protected] Summary: ● Experience 7 years. ● Performing execution and analysis test results. ● Implementation of qa education processes. ● Developing from scratch an automation framework based on the java stack. ● Organizing automation qa processes. ● Setuping CI/CD processes. ● Preparation approach for performance testing. ● Team leading / management at least 5 people; Skills: ● Test automation: Selenium (Selenide), TestNG, Selenium Grid (Selenoid). ● Performance tools: Locust, Gatling. ● Build automation/Continuous integration: Docker, Gradle, GitLabCi, Jenkins. ● Cloud: Azure, Linode. ● Bug Tracking/Test Management: Atlassian JIRA. ● Web debugging tools: Chrome dev tools. ● Programming: Java, Python; ● Version control system: Git; ● Agile: Scrum, Kanban. Work Experience: January, 2019 - till now Senior Software Test Engineer, GlobalLogic Project Role: Lead Automation Tester Tasks and Accomplishments: ● Automation tests creation and execution on 5 sub-projects. ● Performance testing. ● Creation of test automation framework from scratch and maintenance. ● Creation a test plan and strategy. ● Leading and supporting work of qa team; Environment: ● Selenide, TestNG, Git, Gradle, GitLabCI, IntelliJ IDEA, Azure, Report Portal. ● Java, Python, Selenium Grid, Docker, JIRA, DataDog, SendGrid, Locust, Gatling; January, 2015 - January, 2019 Software Test Engineer, EPAM Systems Project Role: Automation Tester Tasks and Accomplishments:
    [Show full text]
  • The 20 Best 2018 Performance Tester Insights
    Whitepaper The 20 Best 2018 Performance Tester insights THE 20 BEST 2018 PERFORMANCE TESTER INSIGHTS 2nd edition 20 speakers from 10 countries 24 hours live 35 cup of coffee 800 registrants 950 stickers Whitepaper The 20 Best 2018 Performance Tester insights This past June, Neotys brought together 20 experts from around the world to share their experience and knowledge regarding techniques, challenges, and best practices associated with load testing for the modern enterprise. The gathering was delivered online as a virtual event. The second annual Performance Advisory Council (PAC) event, proved to be transformational. Attendees were treated to new and innovative practices on the art and science of performance testing. Each presentation provided a wealth of information with insights and techniques aimed at performance testing improvement. The following is a synopsis of several presentations made during the event. We’re happy to share this information in the spirit of creating a more well informed, efficient community of test practitioners. Enabling user story sharing and learning on an international basis is critical to us. Stijn Schepers Performance Testing is Not an Average Game! Stijn Schepers has over 18 years of international experience as a performance test specialist/manager using both Agile (Scrum, SAFe) and Waterfall models. He has worked in Europe, New Zealand, and Australia as a performance engineer testing and optimizing complex enterprise solutions like Oracle: Financials, Forms, Web Center, CRM Applications, JD Edwards, J2EE solutions, Vignette, SIEBEL, SAP, Cúram, IBM Websphere, and Mule. Schepers is a visionary leader with in-depth technical knowledge in concept and practice driving performance testing in the modern enterprise.
    [Show full text]
  • Loadrunner Cloud an Essential Component of the Devops Pipeline
    Product Flyer Application Delivery Management LoadRunner Cloud an Essential Component of the DevOps Pipeline Enable faster release and deployment cycles by taking advantage of agile development methodologies to achieve automated con- tinuous delivery. Micro Focus® LoadRunner Cloud makes it simple to integrate testing into the Development Process and test early and often. LoadRunner Cloud at a Glance: Applying an effective testing process within a Scalability in a Continuous high-speed delivery cycle can be a major chal- ■ Scalability: Testing Environment lenge, and traditional non-automated testing Managing hardware for performance testing A cloud-based solution that eliminates the methods may become a bottleneck. Con tin- tools is always a challenge. It becomes an even dependency on hardware as infrastructure is uous testing helps overcome this problem by bigger challenge in advanced DevOps environ- provisioned in the cloud fully automating testing throughout the delivery ments that have multiple teams and multiple ■ cycle. Micro Focus LoadRunner Cloud is the Automation: pipelines executing performance tests—with ideal solution to help overcome the potential Built in integration with Git, so scripts are managed challenges of applying continuous load testing. the need to manage a larger pool of load gener- in the repository for automatic updates prior to runs ators and controllers. LoadRunner Cloud, elim- ■ inates the dependency on hardware, allowing Collaboration: LoadRunner Cloud is the market-leading, multiple users and teams to connect to a single Project Management support, allowing users to share cloud-based performance testing solution, assets such as scripts, licenses, and load generators designed to support agile teams and DevOps cloud solution.
    [Show full text]
  • Integrating Performance Testing in Your CI/CD Process
    Product Flyer Application Delivery Management Integrating Performance Testing in your CI/CD Process Micro Focus® LoadRunner Cloud Makes It Insanely Simple to Integrate Testing into the Development Process—So You Can Test Early and Often. Everything You Need to Make Solution Overview start the testing process earlier, it’s still difficult Automated Testing Easy There’s no question: Continuous performance to actually build performance testing into the testing is critical to the success of your mobile deployment pipeline. ■ Simple, smart, scalable: and web apps. If you don’t test until the end of SaaS-based, pay-per-virtual-user model allows you the cycle—or if you don’t test at all—you risk Performance testing also needs to add value to get started with just a browser and a credit card. production issues, user complaints, poor re- to the business, not just development teams. The software provides graphical, realistic scripting views, and damage to your brand. It needs to improve the quality of the app, cus- and intuitive dashboards. It easily scales up to one tomer satisfaction levels, and the brand image. million virtual users without requiring hardware. The question is how to make continuous per- For application teams, that means the mental- ■ Enterprise-ready: formance and load testing practical in an age ity must change from simple “record/playback” With cross-team project management capabilities, of ever-accelerating development cycles and testing that occurs late in the product cycle to a it supports open APIs for easier enterprise-wide ever-increasing user expectations. Even if more robust engineering approach that starts integration.
    [Show full text]