Release Testing and Sign-off Process

Android Builds

Tests and spreadsheets are linked from Android test cases.

Daily

Linaro Android LAVA test dashboard monitoring is conducted every working day, to ensure we have an up-to-date track on software quality:

  • Check Linaro Android LAVA test dashboard.
  • File bugs or update bug comment if necessary..
  • Update bug links in LAVA dashboard.

Weekly

"Normal Week"

  • QA team picks the latest / best build for each board, based on the daily results.
  • Release critical tests are executed on all boards and done by the end of Friday.
  • File bugs or update bug comment if necessary.
  • Fill test result spreadsheet, send test summary report by the end of Friday.

The Week Before Release Week

  • QA team picks the latest / best build for each board, based on the daily results.
  • Full test are executed on all boards and done by the end of Friday.
  • File bugs or update bug comment if necessary.
  • Fill test result spreadsheet, send test summary report by the end of Friday.

Monthly Release

Thursday / Friday before release week

  • Android team notifies the QA team of the recommended tip builds to test, based on features landed for the release. If Android team wants to know the current weekly test result of there images, simply refer to the test result spreadsheet. Be advised that at this point, tests may not all be finished since this is Thursday.
  • QA Team performs boot test on images, then update boot test result spreadsheet.
    • If critical problems are discovered, file bugs, notify Android team and Release Team <linaro-release AT lists DOT linaro DOT org>, test new recommended tip build if required.

    • If tip builds all boot successfully, Release Team tags and starts a build for the release branch, then notifies QA Team when they are ready and sent out the final release image link.

Monday / Tuesday of release week

  • QA Team executes release critical tests on all boards
    • If critical problems are discovered, file bugs, notify Android team and Release Team <linaro-release AT lists DOT linaro DOT org>, discuss whether a rebuild is needed or if reversion to a previous weekly build is more appropriate

    • Otherwise, the builds are considered stable enough for release

Tuesday / Wednesday - Thursday

  • QA team performs full tests on all boards.
  • File bugs or update comment; update bug status if necessary.
  • Send out test summary report by the end of Thursday

Ubuntu

Tests and spreadsheets are linked from Ubuntu test cases.

Daily

Linux Linaro ubuntu LAVA test dashboard monitoring is conducted every working day, to ensure we have an up-to-date track on software quality:

  • Check Linux Linaro ubuntu LAVA test dashboard.
  • File bugs or update bug comment if necessary.
  • Update bug links in LAVA dashboard.

Weekly

"Normal Week"

  • QA team picks the latest / best build for each board, based on the daily results.
  • Release critical tests are executed on all boards and done by the end of Friday.
  • File bugs or update bug comment if necessary.
  • Fill test result spreadsheet, send test summary report by the end of Friday.

The Week Before Release Week

  • QA team picks the latest / best build for each board, based on the daily results.
  • Full test are executed on all boards and done by the end of Friday.
  • File bugs or update bug comment if necessary.
  • Fill test result spreadsheet, send test summary report by the end of Friday.

Monthly Release

Thursday / Friday before release week

  • Developer Platform team updates base-files in preparation for release week.

Monday / Tuesday of release week

  • Dev Platform team notifies the QA team of the recommended tip builds to test, based on features landed for the release
  • QA Team executes release critical tests on all boards
    • If critical problems are discovered, file bugs, request respin or revert to previous working build as appropriate, repeat testing.
    • Otherwise, the builds are considered stable enough for release.

Tuesday - Thursday

  • QA team executes full test on all boards.
  • File bugs or update comment; update bug status if necessary.
  • Send out test summary report by the end of Thursday.


CategoryProcess

Platform/QA/Process/ReleaseSignoff (last modified 2013-08-30 07:03:56)