ExecutionStatus Cases - DevOps-MBSE/AaC GitHub Wiki

While working on the unit test improvements, it was found that the ExecutionStatus class may not be implemented consistently through the code base.

The class is defined in aac_execution_result.py and includes statuses for constraint operations and for plugin operations that are not consistently utilized within the code base. There are several spots within constraints where GENERAL_FAILURE is used instead of CONSTRAINT_FAILURE. And it seems PLUGIN_FAILURE is not utilized. Believe a potential flow example would be the constraints would make use of CONSTRAINT_FAILURE, and check would utilize PLUGIN_FAILURE to have a more descriptive failure status. PARSER_FAILURE is another status case that might not be utilized everywhere that it should be and needs evaluated.

Finally, we need to confirm that all of the places within the constraints that return failures right now should be a failure and if any should be a warning and therefore make use of the CONSTRAINT_WARNING status instead.