BlazeMeter vs Wilma

BlazeMeter is an enterprise continuous testing platform for performance, functional, and API testing, with service virtualization and AI-powered test data. It supports tools and protocols used by JMeter and Taurus, including JMeter, Selenium, Gatling, and Playwright. AI-assisted features include test creation, anomaly detection, log analysis, and APM correlation for test triage. Listed CI/CD integrations include Azure DevOps, Jenkins, TeamCity, Bamboo, AWS CodePipeline, GitHub, and GitLab. Service Virtualization can simulate dependent services, including HTTP or HTTPS services, REST and SOAP APIs, messaging systems, and Kafka. Private Locations let customers test applications or create virtual services behind a firewall using Docker or Kubernetes agents on listed Linux distributions. The free Starter plan lists limits of 50 virtual users, one shared load generator, 10 tests per month, and 20 minutes per test. Performance Basic (Annual) costs $99 a year; APIs Small costs $79 a month. A free Chrome extension records web actions and HTTP requests to create JMeter and Selenium scripts.

Wilma is free, GPLv3-or-later software for developing and testing applications that depend on other services. It combines a service stub with an HTTP/HTTPS transparent proxy, allowing teams to capture, decode, save, and forward traffic, including two-way SSL, or generate configured responses. It can operate as a proxy, a stub, or both. JSON files define stub behavior, and configurations can be uploaded or changed through the interface or service while Wilma runs. Real-time interceptors can inspect or modify requests and responses; custom interceptors, condition checkers, and response formatters can be added, including through classes or JAR files. Message Search finds logged request-response pairs. Wilma supports unit, integration, functional, end-to-end, performance, and manual testing. It is available as Docker images, GitHub release ZIP files, or source builds. The application requires JRE 11, while Message Search requires JDK 11. Logging can be controlled and old logs deleted on schedules.