Open ggonzr opened 9 months ago
Related to the next tests cases, I think we should continue with coding more scenarios similar to #1137 focusing on other MC samples that include not frequent steps like DIGI, RECO or others that split the GEN and SIM steps like: B2G-chain_RunIISummer19UL16wmLHEGEN_flowRunIISummer19UL16SIM_flowRunIISummer19UL16DIGIEpsilonPU_flowRunIISummer19UL16HLT_flowRunIISummer19UL16RECO_flowRunIISummer19UL16MiniAOD_flowRunIISummer19UL16JMENtuplesNanoAOD-00002. Then, we could also start coding other tests for checking endpoints that are not directly related with the execution of the previous cases like: gen_logs. @lmoureaux, what do you think about this approach?
The approach sounds reasonable. Do we already test endpoints retrieving information about existing requests like the inject/test commands?
No, not yet. The only group of tests that exists is for the campaign
entity
Update all the McM source code to drop the support for Python 2.
Is your feature related to a problem?
This application still uses Python 2 as the main reference version for its code base. This version has been deprecated since January 2020 and it is required to update it. Also, another motivator is the ongoing OS migration to AlmaLinux 9, newer distributions don’t provide this old package anymore.
Describe the solution you'd like
Initial plan
black
pylint
as a static code analyzer.More details will be included in the comments below.
Linked ticket: PDMVDEV-5