Version used
Context of the issue/feature
When running new suite and DB for it does not exist and auto creation of DBs is disabled - there is no message what happened but suite run fails.
Steps to reproduce
- Make sure that
MongoDBClient allowAutoCreate is set to false (disable auto creation of DBs in AET).
- Run suite (e.g. using
aet.sh) with company and project that does not have DB created.
Result:
Suite is not processed and no progress is presented by suite status endpoint:
{"status":"UNKNOWN","message":""}
From the user (who runs aet.sh) perspective, nothing happens. Internally AET does not process the suite.
Expected:
Suite status endpoint returns proper status (e.g. PROCESSING_ERROR) and message about the problem.
Appendix
This case is already supported by MetadataDAOMongoDBImpl. It looks that this exception is not handled properly.
Version used
AET 2.1.6Context of the issue/feature
When running new suite and DB for it does not exist and auto creation of DBs is disabled - there is no message what happened but suite run fails.
Steps to reproduce
MongoDBClientallowAutoCreateis set tofalse(disable auto creation of DBs in AET).aet.sh) withcompanyandprojectthat does not have DB created.Result:
Suite is not processed and no progress is presented by suite status endpoint:
{"status":"UNKNOWN","message":""}From the user (who runs
aet.sh) perspective, nothing happens. Internally AET does not process the suite.Expected:
Suite status endpoint returns proper status (e.g.
PROCESSING_ERROR) and message about the problem.Appendix
This case is already supported by
MetadataDAOMongoDBImpl. It looks that this exception is not handled properly.