Closed
Bug 1313816
Opened 9 years ago
Closed 9 years ago
Please deploy autopush 1.20.0 to STAGE
Categories
(Cloud Services Graveyard :: Operations: Autopush, task)
Cloud Services Graveyard
Operations: Autopush
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: cloud-services-qa, Assigned: oremj)
References
Details
------------------
RELEASE NOTES
------------------
https://github.com/mozilla-services/autopush/releases
COMPARISONS
https://github.com/mozilla-services/autopush/compare/1.19.1...1.19.2
https://github.com/mozilla-services/autopush/compare/1.19.2...1.19.3
https://github.com/mozilla-services/autopush/compare/1.19.3...1.20.0
TAGS
https://github.com/mozilla-services/autopush/releases/tag/1.20.0
https://github.com/mozilla-services/autopush/commit/5dcb373fd03cf4f1dc7988bb872488d21ba64e55
CHANGELOG
<a name="1.20.0"></a>
## 1.20.0 (2016-10-28)
#### Bug Fixes
* improve handling of JSONResponseErrors ([7dcb0a0d](https://github.com/mozilla-services/autopush/commit/7dcb0a0d2884dc7f717815594324c0c31550f1d5))
* improve handling of JSONResponseErrors (#718) ([29ff0fe4](https://github.com/mozilla-services/autopush/commit/29ff0fe4e959958ba3c6e9578a3cb8a4d4c2ecf4))
#### Features
* skip timestamped messages instead of deleting (#720) ([c2418107](https://github.com/mozilla-services/autopush/commit/c241810711aa8fa84dc8eded89e9aedf3cdea45c), closes [#661](https://github.com/mozilla-services/autopush/issues/661))
* Add integration tests for bridges ([5bc3abe7](https://github.com/mozilla-services/autopush/commit/5bc3abe7b20818c9432d6784a958dced8f755bd8))
* add type hints to autopush/utils.py (#713) ([12a9b7cd](https://github.com/mozilla-services/autopush/commit/12a9b7cd20596a1766d25e6c66db1694de8668b3))
Updated•9 years ago
|
Component: Operations: Deployment Requests → Operations: Autopush
Updated•9 years ago
|
Assignee: nobody → oremj
QA Contact: rpappalardo
Updated•9 years ago
|
Status: NEW → ASSIGNED
Comment 1•9 years ago
|
||
this release has been deployed to STAGE
----------------------------
URL CHECKS (STAGE)
----------------------------
curl -s 'https://updates-autopush.stage.mozaws.net/health' | python -mjson.tool
{
"clients": 0,
"stage.autopush.routerv2": {
"status": "OK"
},
"stage.autopush.storage": {
"status": "OK"
},
"status": "OK",
"version": "1.20.0"
}
curl -s 'https://updates-autopush.stage.mozaws.net/status' | python -mjson.tool
{
"status": "OK",
"version": "1.20.0"
}
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Comment 2•9 years ago
|
||
--------------------------------
SENTRY TEST
--------------------------------
Sentry test -- OK
MY IP: 52.206.211.218
{
"code": 418,
"errno": 999,
"error": "Test Failure",
"message": "FAILURE:Success",
"more_info": "http://autopush.readthedocs.io/en/latest/http.html#error-codes"
}
client_info
{'ami_id': 'ami-906f2587', 'authorization': [Filtered], 'message_ttl': '', 'remote_ip': '52.206.211.218', 'request_id': 'f060986f-5935-4eac-ac52-c240226764c3', 'uri': '/v1/err/crit', 'user_agent': 'curl/7.35.0'}
Comment 3•9 years ago
|
||
--------------------------------
E2E TEST: TOPICS
--------------------------------
Additional E2E-test which includes testing of notification bundling for stored messages
https://github.com/jrconlin/topics - follow README
Desktop (Nightly & Release). -- OK!
Android -- Not Yet Implemented (per :jrconlin)
Comment 4•9 years ago
|
||
----------------------------
E2E-TESTS: VAPID (+Android)
----------------------------
Additional E2E-test which includes VAPID, encryption:
https://jrconlin.github.io/Webpush_QA/
Desktop (Nightly & Release) -- OK
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/
Comment 5•9 years ago
|
||
----------------------------
E2E-TESTS
----------------------------
setting STAGE config to:
dom.push.serverURL = autopush.stage.mozaws.net
DESKTOP E2E PUSH TEST
setup:
start browser with new profile
open: about:config
set: dom.push.loglevel=debug (instead of 'off')
open: Tools > WebDeveloper > BrowserConsole
open: https://mozilla-services.github.io/autopush-e2e-test/
choose: "service-worker.js"
click: "register Service Worker"
click: "subscribe to push"
observe push registration in console
click: "Always Receive Notifications" (in pop-up window)
1. registration test
steps:
click: "XHR to webpush app-server"
observe: successful registration in console
2. message delivery test
setup:
set: Repeat = 2
set: Delay (seconds) = 15
steps:
click: "XHR to webpush app-server"
observe: 2 pop notifications 15 seconds apart
3. payload test
setup:
set: Title = PAYLOAD TEST
set: Body = BODY TEXT HERE
set: TTL = 360
set: Repeat = 4
set: Delay (seconds): 20
steps:
click: "XHR to webpush app-server"
observe:
should see delayed pop notifications with Title, Body specified
4. storage test
purpose: verify that a request is stored on autopush for delayed delivery
setup:
(same as 3 above)
steps:
click: "XHR to webpush app-server
wait for pop notification, then immediately close browser
wait 25 seconds
re-open browser
observe:
should see 3 more delayed messages delivered on browser restart
Comment 6•9 years ago
|
||
----------------------------
SCENARIO TESTING
see: https://github.com/mozilla-services/ap-loadtester/
----------------------------
MULTI-SCENARIO (SOAK) TESTS
[0]. basic
[1]. api_test
[2]. loadtest
run overnight no traceback errors
Comment 7•9 years ago
|
||
----------------------------
SUMMARY
----------------------------
All e2e and API tests passing -- OK
Verifying STAGE.
Status: RESOLVED → VERIFIED
Updated•3 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•