Improper management of technical KOs
/cc @kungnx
We have some old bugs not yet handled. I move them from Jira to here:
-
https://project.squashtest.org/browse/SQUASH-3021 Les KO techniques ne renvoient plus de statut bloqué
When you have a technical KO (incorrect test path, incorrect method or testcase name, git branch not found, ...), the Jenkins pipeline breaks and on the Squash TM side no return is present (stuck at status ready or previous status).
Upstream ITPIs run successfully, but those after the failed one do not run.
No execution is created.
For JUnit, the error is in the execution of the maven command.
Similarly for Robot, it is at the level of the execution of the robot command. -
https://project.squashtest.org/browse/SQUASH-3022 Cucumber : KO technique casse au niveau du tar sans remontée de résultat
When running Cucumber tests and this one is in technical KO (for example feature not found), the execution breaks after the maven command, at the tar level because it does not find the html-report.
The behavior is similar to SQUASH-3021 but the difference is on the command generating the failure.
We therefore have the following ITPIs which are not executed and no return on the Squash TM side.
See the original tickets for logs and screenshots.
We need to check the current situation with this scenarios.
(Fixing these problems may require #250.)
Once fixed, we will have to check that https://project.squashtest.org/browse/SQUASH-2705 Une exécution au statut bloqué récupère des rapports d'autres exécutions is really fixed.
I close the three Jira Tickets. Everything should be now handled here or in GitLab issues linked to this one.
Edit 2023-03-31:
The purpose of this issue is to see if these issues (with no status returned in TM/Jenkins) described in the linked Jira tickets are still present and, in case there are, if they are from a common root cause.
If they would require different resolutions, we will kill this issue and create one per problem.