Use official Python (3) "unittest.mock", instead of home made ones
The following discussion from !39 (merged) should be addressed:
-
@clemenci started a discussion: We should use the official Python (3)
unittest.mock, instead of the home made one.
Security Notice: GitLab has uncovered a widespread malicious npm supply-chain attack that potentially can destroy user data. All teams are required to audit packages. Further information can be found under the Computer Security Report for November 2025 and the original blog post in https://about.gitlab.com/blog/gitlab-discovers-widespread-npm-supply-chain-attack/
The following discussion from !39 (merged) should be addressed:
We should use the official Python (3)
unittest.mock, instead of the home made one.