Closed Bug 1251292 Opened 8 years ago Closed 8 years ago

Please deploy autopush 1.12.1 to STAGE

Categories

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

task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: rpapa, Assigned: oremj)

References

Details

Assignee: nobody → oremj
QA Contact: rpappalardo
Status: NEW → ASSIGNED
----------------------------
HOST CHECKS (STAGE)
----------------------------

EC2 INSTANCE PROPERTIES
region: us-east-1: 
id: i-dc3cf358
tags["Type"]: autopush
tags["Stack"]: autopush
public_dns_name: ec2-54-209-217-195.compute-1.amazonaws.com
launch_time: 2016-02-25T17:55:46.000Z


----------------------------
URL CHECKS (STAGE)
----------------------------

https://updates-autopush.stage.mozaws.net/health:
{
    "status": "OK", 
    "stage.autopush.routerv2": {
        "status": "OK"
    }, 
    "stage.autopush.storage": {
        "status": "OK"
    }, 
    "version": "1.12.1", 
    "clients": 0
}
Response time: 0.342215


https://updates-autopush.stage.mozaws.net/status:
{
    "status": "OK", 
    "version": "1.12.1"
}
Response time: 0.318468
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
----------------------------
VERIFICATION TESTS
----------------------------

all verification tests passing.

(tests outlined below)


FINDMYDEVICE

Able to successfully ring and lock STAGE-configured Flame device (w/ B2G 2.2) x10


HELLO FIREFOX

Able to place several Hello (Loop) calls successfully between Nightly (47.0a1) and GR (44.0.2) w/ STAGE autopush
and verify e2e test calls, room notifications - OK


AP-LOADTESTER: BASIC SCENARIO TEST

ran basic scenario w/ ap-loadtester
NOTE: this is not a loadtest at scale
https://github.com/mozilla-services/ap-loadtester - OK


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://people.mozilla.org/~ewong2/push-notification-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 = 120
set: Repeat = 2
set: Delay (seconds): 15

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 30 seconds
re-open browser
observe:
should see delayed message delivery on browser restart

NOTE:
outlining desktop push tests here for now.  eventually move to readthedocs.
----------------------------
SUMMARY
----------------------------

:oremj has pushed this release to stage and all e2e tests look good. 

Verifying STAGE.

UNITTESTS - OK
travis-ci still in progress, but tests run fine on my lnx box
https://travis-ci.org/mozilla-services/autopush/builds/111808240
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.