Set up Bitbucket Pipelines workflow for coverage reporting.
Add the following job to your bitbucket_pipeline.yaml
. It triggers on pushes to the mentioned branch in the yaml file:
Don’t forget to add your access token to the pipeline secrets under the name “ACCESS_TOKEN”. The access token should have write access to the repo.
The <module_name>
is optional. It is used to specify modules in the case of monorepo structure.
You have to create a .coveragerc file in the project’s root folder to include all the source files in the test coverage calculation.
Example:
When you assign source to ”.” , It checks for every python file in the root folder and its sub directories. You can omit some directories by placing them in the omit section of the file.
With the above configuration:
Set up Bitbucket Pipelines workflow for coverage reporting.
Add the following job to your bitbucket_pipeline.yaml
. It triggers on pushes to the mentioned branch in the yaml file:
Don’t forget to add your access token to the pipeline secrets under the name “ACCESS_TOKEN”. The access token should have write access to the repo.
The <module_name>
is optional. It is used to specify modules in the case of monorepo structure.
You have to create a .coveragerc file in the project’s root folder to include all the source files in the test coverage calculation.
Example:
When you assign source to ”.” , It checks for every python file in the root folder and its sub directories. You can omit some directories by placing them in the omit section of the file.
With the above configuration: