EMResearch
Cannot find StringGene with taint and Thrown exception: No valid input name: { "$ref" : "TfXm", "$id" : "ZsMZb6pJKL0" }
hi @arcuri82 ,
below are the Errors am getting that is resulting in not generating a single successes Test cases
FYI : am Running Spring boot project which has Mongodb Connection ...
what exactly this error explaining
or is it realy the problem with openAPI Schema ( to be honest i dont see any problem in that. as am testing those API's and working fine )
I have another Spring boot service that is not throwing these below errors generating very few successes Test cases
there are a lot of 500 Status codes in faults Test cases
Potential faults: 35 Covered targets (lines, branches, faults, etc.): 2443 Bytecode line coverage: 26% (676 out of 2607 in 170 units/classes) Successfully executed (HTTP code 2xx) 3 endpoints out of 10 (30%) what exactly this Potentia faults 35 means ?
11:14:38.139 [main] WARN o.evomaster.core.taint.TaintAnalysis - Cannot find StringGene with taint: { "$ref" : "EM_17046_XYZ", "$id" : "EM_8548_XYZ", "$db" : "EM_35027_XYZ" } 11:14:38.848 [main] WARN o.e.c.r.service.RemoteController - Failed to register new action. HTTP status 500. Error: 'null 11:14:38.937 [main] WARN o.e.c.r.service.RemoteController - Failed to retrieve target coverage for 188,18,12,194,119,229,261,267,297,302,454,484,543,556,590,598,688,704,717,721,730,733,736,748,770,773,776,778,822,830,841,860,905,913,1046,1058,1084,1112,1142,1164,1167,1220,1229,1237,1245,1252,1260,1269,1270,1294,1339. HTTP status 500. Error: 'Thrown exception: No valid input name: { "$ref" : "TfXm", "$id" : "ZsMZb6pJKL0" } 11:14:38.938 [main] WARN o.e.c.p.e.service.EnterpriseFitness - Cannot retrieve coverage 11:14:38.938 [main] WARN o.e.c.search.service.FitnessFunction - Failed to evaluate individual. Restarting the SUT before trying again
11:24:37.449 [main] WARN o.evomaster.core.taint.TaintAnalysis - Cannot find StringGene with taint: { "$ref" : "EM_31818_XYZ", "$id" : "ZsMZb.pJKN0" }
is Evomaster really works good with MongoDB ? or is it still in Development ?
hi, in this case, "potential" means that 35 bugs are found, but only the user can say for sure that they are bugs. a 500 status code is typically due to bugs in the software, but not always. This should be better discussed in the documentation.
regarding schema, the tests should have comments describing the bug. Note, if the schema is generated automatically, eg with SpringDoc or SpringFox, and it is not fixed with annotations, then you will end up with many, many problems, as automatically derived schemas are very partial. This as well should be better explained in the documentation (which unfortunately at least until May-June ll have no time to update due to other deadlines)
Dear @naveensabavath ,
thanks for trying out EvoMaster and opening an issue here. If you have 10 minutes, we would be grateful if you could fill this survey on test naming strategies #1206. We will use such information to improve EvoMaster. Thanks!