ReleaseEngineering/How To/Verify a New Taskcluster Platform: Difference between revisions

Latest revision as of 15:20, 20 July 2017

making sure api keys exist
making sure that the installer gets localized (on localized builds)
ensure google/etc api keys are in place
ensure information necessary [?] to let EME extensions load.
verify size of zip
verify package naming
verify package icons
Verify TC-dervied builds are byte-for-byte equivalent to buildbot builds#
manually sign build (manual-signed dmg, then task-signed, then full graph)
run talos (bug 1354804) and ensure that performance is on par with buildbot builds
run unit tests
Verify that the en-US+l10n nightlies and associated updated methods work via manual testing
verify updates work as expected - run update verify tests (Softvision QA can help) Example bug 1330008
verify that a build that is updated is signed after update, both for en-US and other locales
Verify that the signature formats match those from buildbot builds

Macosx
Windows
1. Verify that sha's of all files in extracted in the installer match the sha's of files in the zip and as generated after a complete.mar updates us.
Linux
Android

@@ Line 17: / Line 17: @@
 # Verify that the en-US+l10n nightlies and associated updated methods work via manual testing
 # verify updates work as expected - run update verify tests (Softvision QA can help) Example {{bug|1330008}}
+# verify that a build that is updated is signed after update, both for en-US and other locales
 # Verify that the signature formats match those from buildbot builds