The LoadView Plugin for Jenkins
Add LoadView tests to your Jenkins Builds
Discover performance issues earlier and release more reliable applications to production by integrating LoadView performance tests into your CI development process. Generate comprehensive test reports and gain insights into code performance.
Jenkins: Open-source Automation and Continuous Integration
Before we dive into the specifics of the LoadView Plugin for Jenkins, we’ll discuss Jenkins and why is it important.
Jenkins is an open-source automation server built on the Java Virtual Machine (JVM), supporting thousands of plugins for the development, deployment, and automation of software projects. They are the leader in the open-source automation server space. Other companies that provide open-source automation servers are TeamCity, CircleCI, Hudson, Travis CI, Atlassian Bamboo, among many others.
As part of modern software delivery practices, such as shift left testing and continuous integration, developers, testers, and designers all utilize Jenkins to build, deploy, and automate their tests. Over time, as development and testing cycles became shorter and more frequent due to technological advances and the focus on the digital experience, it became apparent that in order to release quality software features – and consistently – teams as a whole needed to become more agile. This meant that testing now “shifted” to the left and happened earlier, typically after the initial code is written. This “test early and often” mantra is especially significant in continuous integration and continuous delivery (CI/CD), where the goal is to be able to consistently and continually release changes.
Continuous integration essentially ditches the need to test from one’s own machine and automatically test every time new code is pushed into shared source repository, which could be multiple time per day. The advantage of continuous integration is that all development work and code can be integrated into the process earlier, helping to identify and fix bugs or errors more quickly and effectively. The quicker you can find and fix software errors, the more likely you won’t have to fix it in production, where it can be more time consuming and expensive.
To extend continuous integration further, teams use continuous delivery practices to automate and control the software release cycles on top of automating the software testing process. Furthermore, teams can employ continuous deployment, which essentially removes the need for almost any human involvement. All changes that pass through your software development stages are automatically released into production.
LoadView: Real Browser-based Load and Stress Testing from the Cloud
The LoadView platform is a flexible load and stress testing platform that addresses the issue of ineffective load patterns, simulating everything from protocol-based tests to real browser-based tests.
Performance testing usually requires additional infrastructure and resources that some organizations may not be able to support. LoadView manages this for you through the platform. The platform is completely cloud-based, so there’s no need to setup or deploy any internal load injectors, manage third-party cloud accounts, or worry about hardware or software requirements.
- Protocol-level and real browser-based testing
- Advanced scripting in 40+ desktop/mobile browsers and devices
- Load curve options – load step, goal-based, and dynamic adjustable curves
- Test from nearly 30 global locations
- Scale from dozens to thousands of virtual users
- Measure response time as perceived by users
- Reuse load testing scripts for monitoring in production
These features that puts the process of performance testing into users’ hands, setting LoadView apart from other load testing solutions on the market today. Read more about all the features of LoadView.
LoadView Plugin for Jenkins Requirements
Utilizing the LoadView Plugin for Jenkins, performance testing teams can easily incorporate real browser-based load testing into their Jenkins test builds. This ensures that applications are continuously being tested and evaluated over longer periods of time. This allows teams to identity and address errors and bottlenecks before code and applications are pushed into production.
*Before using the LoadView Plugin for Jenkins, you must first have an active Jenkins and LoadView account and configure a stress test scenario.
No credit card, no contract.
Create a Unique Identifier for Jenkins Integration
To set up an integration with Jenkins, you will first need to create a Unique Identifier (UID) to use as a LoadView Security Token. To create your UID, follow these simple steps:
1. Log into your LoadView account
2. From the Account menu, select Integrations
3. Select Add Integration
4. Select Stress Testing Web API. A UID will automatically be created.
5. Copy the integration UID to use in Jenkins.
As a general note about Integration types, you can create as many Integration types as needed. Each integration has a Unique Identifier (UID) that will be required during setup. To create an Integration and UID, select the Add Integration button above and select the Integration Type. A secure UID will be created automatically.
LoadView Plugin Installation in Jenkins
1. Log into your Jenkins account
- Select Add Credentials from the Credentials menu
- Select the LoadView Security Token (UID).
2. Configure and validate the credentials
- Kind. LoadView Security Token (UID).
- Scope. Select Global.
- ID. Leave default or specify a unique ID.
- Description. Specify a unique description to distinguish the credentials.
- UID. Paste the LoadView UID from your LoadView account. Once the UID has been added, click Validate UID to make sure Jenkins can access the LoadView API.
3. Select a job and click Configure
- Go to Build > Post-build Actions > Add Post-build Action > LoadView-Run load test scenario
- Specify LoadView Stress Test settings for your Jenkins Build
- Credentials. Select the API key using the description.
- Scenario ID. Paste the stress test scenario ID you want to use in the build. Copy the ID from the scenario page in LoadView.
- Error Threshold. Specify an acceptable percentage of sessions with errors that occur during the test (for example, failed to access the target resource, no keywords/image found, etc.). If the percentage of error sessions is greater than the specified value, the build will be marked as a failure in Jenkins.
- Average Time. Specify a limit for an average response time measured during test execution. If the limit is reached, the build will be marked as a failure in Jenkins.
4. Save your Build Actions
LoadView Test Results
When a test is running, the status of execution is displayed in the Jenkins Console Output in real-time mode.
Once the test has been finished, the results can be found under LoadView Results in the Jenkins Build menu.
- Test duration
- Maximum number of virtual users
- Total sessions
- Successful sessions
- Failed sessions
- Uncompleted sessions
Select More Details to review more comprehensive LoadView performance reports.
All from one convenient load testing platform.