pg_stat_monitor: Automate the Q/A

Description

We need to automate the Q/A process to achieve 90+ code coverage. This should include positive and negative testing.

 

 

How to document

None

How to test

None

Smart Checklist

Activity

naeem.akhter February 8, 2022 at 10:33 AM

naeem.akhter December 9, 2021 at 11:45 AM
Edited

Here are estimates for automated Q/A process,

  • If we automate using traditional sql or bash based regressions, it will require around 3-4 weeks.

  • If we automate using TAP testing framework, effort required would be around 6 weeks. 

In the above given timeframe, 

  • Cover supported PostgreSQL version 11~14.

  • Testing against a build deployment/install, e.g configure, make, make install. 

  • Testing against a package based install, e.g using apt for Ubuntu using Github Actions. 

  • All automation would be done in form of regression test-suite and GitHub actions. 

  • Automated regression/test-suite testing on Centos 7/8 would be supported against a build or package install on a vm, but that won't be implemented in Github Actions as Centos is not supported in Github actions. 

  • We will cover 90+ code coverage through automated regression of supported features, including positive and negative testing for GUC settings.

  • Estimates given don't cover the stress, benchmarking or performance testing. 

  • Estimates given only cover the automation of regressions/test-suite for supported features, and any other setup/change in Github actions using Ubuntu 18 (PG11) & 20 (PG12~14). No other infrastructure or CI/CD process is covered in given estimate. 

 

Done

Details

Assignee

Reporter

Components

Affects versions

Priority

Smart Checklist

Created December 3, 2021 at 9:22 PM
Updated March 5, 2024 at 9:33 PM
Resolved February 8, 2022 at 10:32 AM