Closed
Bug 1450947
Opened 7 years ago
Closed 7 years ago
Please deploy autopush 1.43.0 to STAGE
Categories
(Cloud Services :: Operations: Deployment Requests - DEPRECATED, task)
Cloud Services
Operations: Deployment Requests - DEPRECATED
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: grumpy, Assigned: oremj)
References
Details
Please deploy autopush 1.43.0 to STAGE for QA testing before deployment to production.
Bug Fixes
Remove expiry checks for routing to prevent dropped mobile UAID (8a6cd619, closes #1161)
Features
add megaphone api token auth (1e74f963, closes #1164)
| Reporter | ||
Updated•7 years ago
|
| Reporter | ||
Comment 1•7 years ago
|
||
URL and Sentry Checks
pytest --env=stage --api-version=1.43.0 tests/test_urls.py tests/test_sentry.py
========================================================= test session starts =========================================================
platform darwin -- Python 2.7.10, pytest-3.0.7, py-1.5.2, pluggy-0.4.0 -- /Users/chartjes/.local/share/virtualenvs/autopush-integration-tests-_LJXrNHM/bin/python
cachedir: .cache
rootdir: /Users/chartjes/rpappalax/autopush-integration-tests, inifile: tox.ini
plugins: variables-1.6.1, testrail-1.1.3
collected 2 items
tests/test_urls.py::test_status_endpoint PASSED
tests/test_sentry.py::test_generate_logcheck_error PASSED
Status and API version checks pass
Sentry reports the following information:
{'ami_id': 'ami-08993b75', 'authorization': [Filtered], 'message_ttl': None, 'python_version': '2.7.13 (84a2f3e6a7f8, Oct 03 2017, 11:00:55)
[PyPy 5.9.0 with GCC 6.2.0 20160901]', 'remote_ip': '108.160.90.26, 172.31.62.145', 'request_id': 'f3317c2f-762e-473d-b40f-ab9e63cfb257', 'uri': '/v1/err/crit', 'user_agent': 'python-requests/2.14.2'}
| Reporter | ||
Comment 2•7 years ago
|
||
----------------------------
E2E-TESTS: VAPID (+Android)
----------------------------
Test succeeds on STAGE.
Additional E2E-test which includes VAPID, encryption:
https://jrconlin.github.io/Webpush_QA/
Android (Nightly, Release) -- OK
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/
| Reporter | ||
Comment 3•7 years ago
|
||
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
Test #1
* 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
Test #2
* click on 'subscribe to push'
* change values for 'repeat' and 'delay' to have at least 2 messages with at least 5 seconds between them
* click on 'XHR to webpush app-server' and verify the number of messages sent and the delay between them is accurate
Passes on STAGE
| Reporter | ||
Comment 4•7 years ago
|
||
--------------------------------
E2E TEST: TOPICS
--------------------------------
Additional E2E-test which includes testing of notification bundling for stored messages
https://github.com/jrconlin/topics - follow README
Set dom.push.serverURL to wss://autopush.stage.mozaws.net/
Desktop (Release). -- PASS on stage
| Reporter | ||
Comment 5•7 years ago
|
||
QA validates 1.43.0 on STAGE and gives the okay to deploy to PRODUCTION
| Assignee | ||
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•