digitalbanking drivers

[omursahin]

Please check my comment on the README:

Note: for digitalbanking, run the fuzzer with --endpointExclude "/generateData".
That endpoint loops on its request parameters with no upper bound, and a large value makes the SUT unresponsive for the rest of the experiment.
The white-box drivers already skip it.

[arcuri82]

@omursahin hi. we shouldn't skip endpoints. in WB, we have kill switches in the instrumentation. in BB, it will be interesting to add features to automatically exclude endpoints from search if connection timeout a few times (which don't do yet, but should in future)

[omursahin]

@omursahin hi. we shouldn't skip endpoints. in WB, we have kill switches in the instrumentation. in BB, it will be interesting to add features to automatically exclude endpoints from search if connection timeout a few times (which don't do yet, but should in future)

@arcuri82
I can remove it, but removing it will cause the application to crash and stop working. EvoMaster timeouts are not useful in this application.

A request like GET /generateData?noOfCustomers=5000000 eventually causes a java.lang.OutOfMemoryError: Java heap space. The root cause is in BankService.createCustomerAccount: the endpoint tries to create 5,000,000 customers, and the application runs out of memory while generating them.

[arcuri82]

@omursahin i see... i need to think a bit about how to best handle a case like this. i guess you can work on the other SUTs meanwhile