Closed Bug 1529261 Opened 6 years ago Closed 6 years ago

Please deploy and test autopush 1.53.1 on STAGE

Categories

(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: grumpy, Assigned: oremj)

Details

QA to test autopush 1.53.1 on STAGE, including additional testing on Android devices that FCM and GCM are working correctly

Assignee: nobody → oremj

URL AND SENTRY CHECKS

pytest --env=stage --api-version=1.53.1 tests/
======================================= test session starts ========================================
platform linux2 -- Python 2.7.15, pytest-4.1.0, py-1.7.0, pluggy-0.8.0 -- /home/chartjes/.local/shar
e/virtualenvs/autopush-integration-tests-EcyFGSW_/bin/python
cachedir: .pytest_cache
rootdir: /mnt/c/Users/chartjes/mozilla-services/autopush-integration-tests, inifile: tox.ini
plugins: variables-1.7.1, testrail-2.3.2
collected 2 items

tests/test_sentry.py::test_generate_logcheck_error PASSED [ 50%]
tests/test_urls.py::test_status_endpoint PASSED [100%]

Sentry reported the logcheck error that was deliberately generated. It reported the following details:

{'ami_id': 'ami-0e2bba304008a6af5', 'authorization': [Filtered], 'message_ttl': None, 'python_version': '2.7.13 (ab0b9caf307d, Apr 24 2018, 18:04:42)
[PyPy 6.0.0 with GCC 6.2.0 20160901]', 'remote_ip': '108.160.90.26, 172.31.30.24', 'request_id': 'bc6d6949-1332-4254-b607-39c651268cb5', 'uri': '/v1/err/crit', 'user_agent': 'python-requests/2.21.0'}

whatsmyip.com reports my IP address as 108.160.90.26

E2E TEST: TOPICS

Additional E2E-test which includes testing of notification bundling for stored messages

Install Docker, grab the image chartjes/topicserver-tests and then start the container using the command:

docker run -d -p 8200:8200 chartjes/topicserver-tests

Start Firefox with a clean profile

Set dom.push.serverURL to wss://autopush.stage.mozaws.net/

Go to http://localhost:8200

Follow the instructions on the web page

Desktop (Release). -- PASS on stage

E2E-TESTS: VAPID (+Android)

Test succeeds on STAGE.

Additional E2E-test which includes VAPID, encryption:
https://jrconlin.github.io/Webpush_QA/

Android (Nightly, Release) -- PASS

NOTE:

This page can also be used to test Android, however,
on STAGE / PROD gcm path + senderID must be appended (see below).
oremj> the sender ids are 965234145045 and 829133274407 (for both STAGE & PROD)

STAGE:
dom.push.serverURL = https://updates-autopush.stage.mozaws.net/v1/gcm/829133274407

PROD:
dom.push.serverURL = https://updates.push.services.mozilla.com/v1/gcm/829133274407

unlike paths for desktop (uses sockets):

STAGE:
dom.push.serverURL = wss://autopush.stage.mozaws.net/

PROD:
dom.push.serverURL = wss://push.services.mozilla.com/

E2E-TESTS

DESKTOP E2E PUSH TEST

Install Docker, grab the image firefoxtesteng/autopush-e2e-test and then start the container using the command:

docker run -p 8201:8201 firefoxtesteng/autopush-e2e-test

Using a fresh profile for Firefox, go to to http://localhost:8201

go to about:config and set dom.push.serverURL = wss://autopush.stage.mozaws.net

with 'service-worker.js' selected click on 'Register Service Worker' and see the messages:

registering service worker
registered service worker. scope: http://localhost:8201/

alter the 'Title' and 'Body' fields in the Notifications Property form to unique values
click on 'pop Notification' and verify the notification contains your expected Title and Body
click on 'close Notification' and verify the notification is closed

PASSES on STAGE

FCM/GCM Testing on Android

Using an Android device with Firefox configured to point to the staging push server, the following page was loaded and the instructions followed to verify functionality:

https://mozilla-services.github.io/WebPushDataTestPage

PASS on stage

QA validates autopush 1.53.1 on STAGE and approves pushing it to production.

Flags: needinfo?(oremj)
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(oremj)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.