Systems | Development | Analytics | API | Testing

Load Testing

Best website load testing services

Website load testing services determine how websites deal with online traffic. Too often, people equate it with performance testing. However, load testing is just a type of website performance testing. Other types of performance testing include endurance testing, volume testing, scalability testing, spike testing, and stress testing. In website deployment, it is common that transactions may fail and systems crash. It is due to concurrent demands on the website and adjustment over resources.

Testing without limits: xk6 and k6 extensions

k6 v0.29.0 introduced xk6 and k6 extensions to the k6 community. 🎁🎉💪 You can now extend the functionality of k6 using Go-based k6 extensions and import them as JS modules in your k6 script. This feature opens the gates for anyone to use existing k6 extensions and write custom Go extensions for special requirements. Before this release, importing JavaScript libraries was the only possibility to extend k6.

What's New In Loadero (November 2020)

November was a big month for Loadero in terms of updates. We were working on the compute units feature for a long time and are very happy that now we provide our customers even more control over configuring test participants. We improved our test runner stability and made some important fixes. We are proud to share what has been updated and are sure that this will help you to run even better tests with us.

Week of Testing Day 4: Streaming results to the cloud and stepped load profiles on k6

Nicole discusses how to stream the results of load tests run locally to the k6 Cloud and how to recreate a stepped load profile using k6, compared to a load testing tool like JMeter. Note from Nicole: I realized after this video that I was mixing `let` and `var` in this video. They have different implications on scope, and I would recommend you use `let` or `const` in your own scripts. Also, there are other ways to achieve the stepped load profile, but this is one way to do it.

Agile Software Release Checklist Manifesto

How do you manage to release often without major issues? Create a checklist for your software releases, a list of steps to blindly follow every time release a new piece of software. Here is an example of what steps your list should contain: This list can go on and on, by I would suggest that every team should have a similar checklist. This checklist should be reviewed and updated every 1-2 weeks (doesn’t matter if you do Scrum or Kanban), most likely at the team retrospective meetings.