When running code analysis, what does Copado look for in user stories?

When running code analysis in Copado, the primary focus is on identifying "violated rules" within user stories. This process involves examining the code for adherence to predefined standards and best practices that help ensure quality and maintainability. Violated rules indicate specific issues such as code smells, potential bugs, or deviations from coding conventions that may lead to problems in the delivery pipeline. By flagging these violations, Copado enables development teams to address issues proactively, improve code quality, and reduce technical debt.

Static code analysis settings, custom settings, and pipeline configurations play roles within the broader context of a CI/CD process but are not the primary focus during a code analysis of user stories. While these elements are important for setting up the environment and ensuring the overall effectiveness of the development lifecycle, the actual analysis is centered on detecting the specifics of rule violations that could hinder the project's success.