Skip to content

QA Activities

Rajiesh edited this page Feb 27, 2020 · 3 revisions

List of activities to be done before a release to call it QA Done,

Ensure test pipelines are passed for the last commit on the gocd/gocd repo master branch,

  • smoke
  • smoke-on-cloud
  • regression - SPAs
  • installer-testing

enterprise repo master branch,

  • regression-pg-gauge
  • installer-testing
  • Upgrade-testing
  • BC-testing
  • migration-test
  • performance - Call to execute performance test can be taken based on the need. Depending on the changes going in a release a call can be taken if performance test needs to be executed.

Manual activities:

  • Testing on Windows - Regression does not cover Windows installers and testing feature on windows. General tests executed on windows

    • GoCD server and agent installers with and without PG addon
    • Installer upgrade with and without PG addon
    • If any plugin related changes test the plugins on windows
  • Cross browser testing - performed using https://crossbrowsertesting.com/ - credentials are in the vault

    • Specifically IE Edge 14 to latest(depends on the GoCD supported browsers)
    • All other supported browsers(regression takes care of firefox, basic test on other supported browsers will help)
  • New/Improved features and Bug Fixes testing

    • New/Improved features to be tested manually.
    • Identify scenarios to be automated and add to regression suite.
    • Project wall comes handy to help in planning these tests
  • Exploratory testing