Blazemeter's UI and testing infrastructure has been recently updated to "Version 4" or what we commonly refer to as "V4". You can use our new and improved test creation page to experience the following benefits:
Same intuitive experience for Gatling, The Grinder, Selenium, etc...
Go beyond JMeter, using the best tool for the task at hand. Now any supported open source testing tool gets the same intuitive experience we provide for JMeter. Run a Gatling test by uploading a .scala file into the test create screen's Scenario Definition section. Same goes for The The Grinder, Selenium Java/Ruby/Python and others. Need additional files distributed to every test engine? Drop them in the same place and go!
Multiple ramp-up steps (without needing a plugin)
Ramping up in multiple steps allows you to observe system behavior at various load levels, letting your systems stabilize for a bit before moving on to the next level. We've made it easier to implement multiple ramp-up steps right from the UI:
Multiple locations from a single test create screen
Distribute your test across geographic locations by simply pressing (+) in the Load Distribution section of the test create screen:
Auto-save (no more missed configuration changes!)
Configuration changes are now auto-saved for you. If you have ever made a change and launched without hitting save first, you'll appreciate the difference. We also populate the test name with a default based on the date and time, leaving you with one less thing to do before launch if you are in a rush.
Simplified "no console" architecture
We've eliminated consoles and the "sessions" they created when running multiple engines.
Each test now runs in a single "flat" structure, no matter how many locations or engines. If you run multi-location tests, run tests with more than 14 engines, or use Private Locations, you will notice these improvements:
- Streamlined reporting: Drill-down by scenario and location from one report.
- Fewer calibration runs, simpler test configurations: Without consoles, you don't need to run engine-to-console ratio calibration tests or configure multi-tests to reduce the engine-to-console ratio. Just calibrate for single-engine performance and go!
- Simplified Private Location planning: No need to estimate how many extra "ships" will be needed for the console role when planning Private Location capacity. Now every ship in your Private Location harbor is available to run tests.
Let's get started!
Jump on in! It all starts on the New Test Create Screen.
NTC Feedback? Bug to report?