About Blazemeter chrome extension
A Browser Performance Test operates similarly to script-based performance tests, but the test analyzes browser interactions instead of running conventional scripts. This pre-GA (Generally Available) feature is currently accessible to a subset of enterprise customers. If you are an enterprise customer and are interested in accessing this feature before GA, contact support-blazemeter@perforce.com. This test type has the same features as a performance test, but it uses an embedded Selenium script to execute the test directly in a browser. When running Browser Performance Tests, keep in mind that each virtual user consumes 100 Variable Unit Hours (VUH). Thus, a test with 10 virtual users will consume 1,000 VUH (10 users × 100 VUH each). Plan your tests accordingly to manage resource usage efficiently. Why Use Browser Performance Tests? Create a Browser Performance Test Browser Performance Test Best Practices Why Use Browser Performance Tests? Browser Performance Tests are particularly useful in the following scenarios: When correlation Is unavailable or infeasible: Cases where auto-correlation plugins cannot be used due to proxy settings or other restrictions, making manual UI recording a practical alternative. For example, many organizations have security policies that prevent the use of auto-correlation plugins and traditional JMeter scripts. Complex UI testing: Applications with dynamically generated UI elements where element names or HTTP calls are unknown. Limited resources: Users who lack the time, skills, or access to write or manage complex test scripts. Prerequisites To edit Browser Performance Tests, you must understand the following concepts: Objects (GUI elements such as buttons and fields), Actions (such as click or select), and Group Actions. This document includes references to a third-party product, Google Chrome. The user interface and usage of third-party products are subject to change without notice. For the latest published information about Google Chrome, see the Google Chrome help center. Create a Browser Performance Test Follow these steps: From the Home screen, click the Performance tab. Click Create Test. Select a project. Click Browser Performance Test. The Configuration tab for the test opens. Define your Scriptless test in one of the following ways: Record test scenarios in ChromeVerify that you have the BlazeMeter Extension installed. For more information, see The BlazeMeter Chrome Extension.To record test scenarios for browser performance tests using the BlazeMeter Chrome extension, ensure you are using version 6.6.0 or higher.Click Start UI Recorder on an empty canvas. A new browser window opens. The Chrome extension opens.Open your web app and run your test. For more information, see Chrome Extension - Record.When you're done, click Stop Recording in the Chrome Extension. Click Run.In the menu, click Browser Performance (Selenium).The recorded test opens On the Test Configuration page.Build test scenarios out of building blocksDrag Actions from the Groups and Actions tabs
Key features of the Blazemeter chrome extension that are enabled through these drivers include:
- Running a Performance Test - BlazeMeter
- BlazeMeter 6.6.3 - Download, Review
- Importing and Exporting Tests - BlazeMeter
- Creating a JMeter Test - BlazeMeter
- Calibrating a JMeter Test - BlazeMeter
- Calibrating a Taurus Test - BlazeMeter
- Creating a Performance Test - BlazeMeter
To Create Groups A custom Group contains multiple Actions that occur together in a given order. For example, you can create a custom "Login" Group that contains a sequence of three Actions, "Enter User ID," "Enter Password," "Click Submit." Groups are useful because they can be shared, but the use of groups is not mandatory to create scenarios. You add Groups to a scenario in the same way as you add single Actions. To create a Group directly from the Test Definition, drag a sequence of Actions into the Scenario Editor, and select their check boxes. The selected steps must be consecutive without gaps. Then enter a name for the Group and click Save As Group Action. You can nest Groups inside other Groups, but you will not be able to drill down and edit nested Groups directly in the Scenario Editor. How to Edit Groups From the Test Action Library, you can edit only the name and description of a Group. You edit the Actions, Objects, and values inside a Groups from the Scenario Editor. Such local changes are automatically saved only in the current scenario. You can overwrite the values of the original Group in the Test Action Library, or choose to save your changes as a new Group in the Test Action Library. Find the Group in the Scenario Editor and expand it.If you cannot find the Group in the Scenario, use the Test Action Library to find where the Group is used. Click the Edit button (pencil icon) to edit elements of the Group. Debug your test to validate your changes. (Optional) Click Override Group Action to save your changes to the shared Test Action Library. If you overwrite Groups, your changes affect other test scenarios (and other users) that embed shared resources from the Test Action Library. If you save your changes as a new Group, the new Group becomes available to other users through the Test Action Library without impacting existing tests. Browser Performance Test Best Practices Follow the Browser Performance Test best practices to gain the most insight and information from your tests. Following the best practices can also help you avoid common issues found when creating tests. Recorder Best Practices While creating tests using the BlazeMeter Chrome extension, the test contains only one step. All data from your test is contained in the one step. Adding steps to your test can help you organize the data from your test. Go to your website and open the BlazeMeter Chrome Extension. Click Start recording. Begin creating your test. For each new section of the test, add a Label and click Add Step. Create as many steps as needed for your test. You can see
