The first open-source AI-driven tool for automatically generating system-level test cases (also known as fuzzing) for web/enterprise applications. Currently targeting whitebox and blackbox testing of Web APIs, like REST, GraphQL and RPC (e.g., gRPC and Thrift).
According to jest, test files are searched based on the naming:
testMatch: **/__tests__/**/*.[jt]s?(x), **/?(*.)+(spec|test).[tj]s?(x) - 0 matches
If I got it correctly, the files currently are generated using the schema EvoMaster_XX_Test.js.
So the generated files needs to be renamed manually to get them executed using jest. Maybe the automated naming can be changed to EvoMaster_XX.test.js. Or store the files automatically in folder __tests__. But as user I would expect naming as EvoMaster_XX.test.js
Other important info:
version of EvoMaster (EM) used: 3.0.0
how EM is run (eg, if from JAR or from one of its OS installers): OS Installer
version of applicable runtimes (eg, JVM, NodeJS and .Net). For Java, can paste the output of java --version: openjdk 17.0.10 2024-01-16
command-line options used to run EM
/opt/evomaster/bin/evomaster --blackBox true --bbSwaggerUrl http://localhost:3000/api-json --outputFormat JS_JEST --maxTime 30s --ratePerMinute 60 --writeStatistics true
According to jest, test files are searched based on the naming:
testMatch: **/__tests__/**/*.[jt]s?(x), **/?(*.)+(spec|test).[tj]s?(x) - 0 matches
If I got it correctly, the files currently are generated using the schema
EvoMaster_XX_Test.js
. So the generated files needs to be renamed manually to get them executed using jest. Maybe the automated naming can be changed toEvoMaster_XX.test.js
. Or store the files automatically in folder __tests__. But as user I would expect naming asEvoMaster_XX.test.js
Other important info:
java --version
: openjdk 17.0.10 2024-01-16/opt/evomaster/bin/evomaster --blackBox true --bbSwaggerUrl http://localhost:3000/api-json --outputFormat JS_JEST --maxTime 30s --ratePerMinute 60 --writeStatistics true