We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AET 2.1.6
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.
MongoDBClient
allowAutoCreate
false
aet.sh
company
project
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.
PROCESSING_ERROR
This case is already supported by MetadataDAOMongoDBImpl. It looks that this exception is not handled properly.
MetadataDAOMongoDBImpl
The text was updated successfully, but these errors were encountered:
Asia95
Successfully merging a pull request may close this issue.
Version used
AET 2.1.6
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
MongoDBClient
allowAutoCreate
is set tofalse
(disable auto creation of DBs in AET).aet.sh
) withcompany
andproject
that does not have DB created.Result:
Suite is not processed and no progress is presented by suite status endpoint:
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.The text was updated successfully, but these errors were encountered: