Bazel vs EvoMaster

Bazel is a free, open-source tool for automating software builds and tests across languages and platforms. Projects define targets in BUILD files using Starlark, which can also be used to create custom rules and macros. Bazel caches prior work and rebuilds what needs to change, while running tasks in parallel. It supports languages including C++, Java, Kotlin, Python, Go, and Rust, with outputs for desktop, server, Android, and iOS. Bazel runs on Linux, macOS, and Windows, and the documentation describes builds with 100,000 or more source files across multiple repositories. Sandboxing can make builds and tests more hermetic, and failures return a non-zero exit code for basic CI integration. Teams can share outputs through a remote cache, but must select and maintain its backend and secure access because it can contain binaries. IDE options include plugins for IntelliJ, Android Studio, CLion, and Visual Studio Code, plus Xcode integration. Bazel is not well suited to uncached deployment steps that change cloud configuration.

EvoMaster is a free, open-source tool that uses fuzzing to generate system-level tests for web and enterprise applications. It targets REST, GraphQL, and RPC APIs, including gRPC and Thrift. Black-box mode works with APIs in any programming language, while white-box mode analyzes JVM bytecode. Generated tests can be JUnit 4 or 5 in Java or Kotlin, or suites in Python or JavaScript. More than 30 oracles check issues including HTTP 500 responses, schema mismatches, BOLA, and SQL injection. White-box testing can analyze SQL and MongoDB interactions with PostgreSQL, MySQL, H2, and MongoDB support. Authentication accepts headers and cookies, including tokens or cookies obtained from a login endpoint. REST testing requires OpenAPI 2.0, 3.0, or 3.1. PyPI is the recommended installation route, with Docker and an uber-fat JAR also available. EvoMaster runs on Linux, macOS, Windows, and self-hosted environments, and integrates with GitHub Actions through a custom action.