Testing steps in Bitbucket Pipelines
A key step that may be done on a pipeline for continuous integration typically comes post-build. Testing immediately after the build allows for defects to be found and sorted out, guaranteeing better quality in the code base.
The testing steps in this recipe utilize a category of testing called static analysis. With static analysis, the files in the build are scanned to see whether they contain logical errors, security vulnerabilities, or other issues.
Linting is another type of scanning technique that performs tests by evaluating the syntax and structure of the code base. It can also determine whether the code base being evaluated meets specific coding standards.
We will examine different methods of invoking linting and scanning from Bitbucket Pipelines.
How to do it…
Depending on the language, a linting utility may be part of the suite of tools for developing in that language. Let’s see how that works with Bitbucket...
