Providing your clients with excellent load testing and JMeter performance testing reporting is one of the most desired outcome after assessing the performance of their websites or APIs.

And rightfully so, showing results for your cloud tests will improve customer happiness and avoid churn rate.

With Whitelabel Reports from LoadFocus you can generate elegant white label reports that will demonstrate to them the ongoing commitment you have to load testing and JMeter load testing.

White Labelled Reports

Within our Pro plans, you can choose our White Label option and you will be able to brand PDF reports with your own logo & company…

Jenkins is one of the most popular CI/CD open source tools in the market at the moment.

To get a better understand why is it useful to use Jenkins or a CI/CD tool, let’s dive in a brief description to better understand what is Continuous Integration/Continuous Delivery (CI/CD).

What is Continuous Integration (CI)?

Continuous integration (CI) is a software process which helps developers and tech people better manage code changes in their repositories, dealing with multiple branches and features and merging all these code changes back to a shared branch, master.

Pros of Continuous Integration (CI)

• Continuous integration (CI) makes it easier to find and fix bugs quickly.
• Continuous integration…

Load Testing Your Application Using JMeter just got way easier with JMeter Load Testing Cloud tool from LoadFocus.

You can upload your JMeter test scripts and run tests in just a few steps with our new JMeter Cloud Load Testing Tool.

1. How to run a new load test:

1. Choose from multiple world cloud locations
2. Set the number of virtual users (threads), duration, ramp up time and ramp up steps that your JMeter test will use
3. Upload your JMeter test script (.jmx) file and click Execute.

Note: you can also upload a configuration CSV file (.csv) along your JMeter test script.

You can run your JMeter tests in…

Agile methodology nowadays, Scrum or Kanban, is completely different from what we were used to when was it was first presented to us.

We switched from Scrum to Kanban to some hybrid Agile Scrum/Kanban methodology that worked pretty well for us.

Scrum

We used to have 2/4 weeks sprints, with sprint retros and plannings/feature kick-offs.

In an attempt not to be forced to deliver big features in such a small timeframe (2/4 weeks) and also not to raise the team pressure/stress on plannings and commit to specific set of features, we decided to switch to Kanban.

Kanban

With Kanban, we discovered that…

KissFront is a web performance monitoring tool running Lighthouse continuously or on-demand (using Lighthouse as a service) to monitor your website performance and get insights on speed with modern performance metrics.

It uses Lighthouse as a Service to provide regression testing for developers and product people.

Provides five categories of feedback, ranking from zero to 100. Lighthouse Audit references: Performance, Progressive Web App, Accessibility, Best Practices, SEO.

Performance: Audits for metrics like First Contentful Paint or First Meaningful Paint.

PWA: Checks your site’s level of completeness against the baseline Progressive Web App Checklist.

Best Practices: Looks for everything from HTTPS…

From collapsable tabs that close themselves after certain amount of time, or AI algorithm identifying the unused tabs and storing them in an area that may be called Staled Tabs (tabs the browser thinks you don’t need anymore), to Better Search in the History Tab and Performance & Security issues identified and displayed right by the browser in a special area for Website Improvements.

Why do we care so much about a small button that does a little thing in a hidden part of the Developer Tools, and why not create features with much more impact for the billions of…

Writing UI tests that are resilient and easy maintainable is hard. Everyone knows that UI tests are slow and flaky but using a few best practices can make the job of implementing and maintaining UI tests a little more easier.

Here are some best practices that we found useful:

1. use the page object model/robot pattern; this makes the tests easier to understand and update
2. make the tests run independently from one another and still pass; not fulfilling this will make your tests flaky and give weird behaviours on different environments
3. use data-*(data-test/data-testid) attributes so that we can keep the tests independent from the changes in the CSS or JS (ex. button id=”main” class=”btn btn-large” data-test=”submit-login-btn”); this will make your tests more resilient to changes in CSS or JS
4. use more assertions in a single test as the framework should give…