-
Introduction to Performance testing with mabl
-
Introduction to Performance testing with mabl learning check ✅
- Browser performance testing
-
Browser performance tests
-
Measuring browser performance
-
Browser performance testing with mabl learning check ✅
- API performance testing
-
API performance tests
-
Measuring API performance tests
-
API performance testing with mabl learning check ✅
- End-to-end performance flows
-
E2E Performance flow
- Feedback and Summary 👏
-
Feedback 👏
-
Summary
Performance Testing with mabl
Build quality applications with browser and API performance testing in mabl's unified platform
Performance is an essential element of every application. At mabl, we want to help you build and execute browser and API performance tests that seamlessly integrate into your end-to-end testing strategy. This 6-part course will help you prepare for automating your Performance testing strategy, navigate the mabl App to build and execute browser and API performance tests, and review test output to bring quality to the forefront of your automation efforts.
This course is for anyone looking to build a better understanding of their Performance testing strategy or create performance tests in the mabl API trainer, including importing previously created browser or API tests, setting a variety of concurrency, duration, and failure criteria metrics, and reviewing test output to build baseline or comparative performance tests.
Following this course, the learner will be able to:
- Define performance testing
- Outline performance testing as essential
- Prepare resources and API documentation
- Build a browser/API performance test in mabl
- Outline browser-specific and API-specific performance metrics
- Execute browser/API performance tests
- Review the browser/API performance test output
- Identify trends in your application’s performance
- Prioritize test results by impact to your application
- Build and execute an E2E performance test in mabl
- Review test output to pinpoint performance metrics
- Create a quality-driven testing strategy