Continuous Inspection involves our codebase being run through a set of tools that enforce the quality, and inform the developers of any issues that may be found in the code. We use the following tools in BCDevOps and other Projects.
Postman Collection / Newman Runs (BDD API Testing)
Selenium/Browser Stack (or other browser-testing tools)
pgTap (psql schema and procedure testing )
This ticket can likely be split into multiple tasks - likely one for each of the tools mentioned above. SonarQube should be the first one implemented as its provides the greatest value when calculated against effort for implementation.
Acceptance Criteria:
C-Insp tool installed (containerized) in the OpenShift Tools Namespace
Tool configured for use with our stacks (python, view, postgres)
Job created in the pipeline to run the scans/tool against PRs with the option to fail a build given certain outcomes.
Continuous Inspection involves our codebase being run through a set of tools that enforce the quality, and inform the developers of any issues that may be found in the code. We use the following tools in BCDevOps and other Projects.
This ticket can likely be split into multiple tasks - likely one for each of the tools mentioned above. SonarQube should be the first one implemented as its provides the greatest value when calculated against effort for implementation.
Acceptance Criteria: