PRDE - Story default text according to the team DoR (Definition of Ready)

01 - PERSON OF CONTACT (PERSON THAT CAN ANSWER QUESTIONS ABOUT THE PROBLEM):

@Renan Schroeder
02 - STORY BRIEFING (AS A < PERSONA >, I [WANT TO] < NEED >, [SO THAT] < GOAL >):

03 - PROBLEM (WHAT'S THE CURRENT PROBLEM SCENARIO OR PAIN TO BE RESOLVED?):

The unit test AIProcessTaskProcessorTest.checkDockerImageExists_verify_invalid_dockerImageInfo is failling in develop branch, because now we are getting 403 response code from GET - https://gcr.io/v2/invalidproject/invalidimage/tags/list instead of 400 (Bad request).

04 - GOAL (DESCRIBE THE PROPOSED SOLUTION):

Analyze if we need to coverage bad request response behavior with method AIProcessTaskProcessorTest.checkDockerImageExists_verify_invalid_dockerImageInfo and, if not, replace by some unit test to guarantee forbidden use cases, as the result of this unit test.

05 - WHO CAN USE THIS FEATURE (USER ROLES):
06 - ACTIVITY DIAGRAM (ACTIVITY DIAGRAM LINK AND IMAGE):
07 - STEPS (ACTIONS TO BE PERFORMED LINKING TO SCREENSHOTS):
08 - ALTERNATIVE STEPS:
09 - ASSETS (FIGMA LINKS, RELEVANT DOCUMENTATION LINKS, JSON EXAMPLES, ETC):
10 - ACCEPTANCE CRITERIA:

• Back to pass unit test DockerBuildTaskProcessorTest.validateGitAndDockerInfo_invalid_gitRepoUrl_value; or
• New unit test to coverage forbidden response of request {{GET - https:// {docker-registry}

  /imagePath/tags/list}}.