1102194 - Expose Simple Push in the load tests

Status: RESOLVED FIXED

(Hello (Loop) :: Server, defect)

Description

[Tarek Ziadé (:tarek)]

We'd like to be able to run the Loop load tests against a specific simple push endpoint.

This will help ops/qa to smoke test a specific Loop+SP combo.

Comment 1

[Rémy Hubscher (:natim)]

Endpoint or URL? Would you like to configure wss://push.stage.mozaws.net or https://push.services.mozilla.com/{token}

Comment 2

[Tarek Ziadé (:tarek)]

The whole URL is what I call the endpoint. The use case is to be able to run the tests against any SP server.

Comment 3

[Alexis Metaireau (:alexis)]

So, it seems this is to load test SP with the loop scenario in mind.

Ben, I'm not clear what this means in terms of APIs. Is it okay if we always PUT the same URL, or does it need to be a different one each time?

(e.g. do we need to do a websocket connection to get a SP endpoint before giving it to loop server in our load tests?)

Comment 4

[Ben Bangert [:benbangert]]

The endpoint URL is valid forever once its been issued. You'll need a client connected for notifications to actually go through of course. I assume you mean LP (Loop-Push), as SP is for SimplePush which loop is no longer using.

Comment 5

[Rémy Hubscher (:natim)]

Thank you Ben for this, so this is the scenario I am seeing for this:

   Add a loadtest parameter that let use configure the SP endpoint so we can see what's going on with the websocket.

Tarek does this will meet your requirements?

Comment 6

[Tarek Ziadé (:tarek)]

sounds good

Comment 7

[Rémy Hubscher (:natim)]

Attachment: Link to Github PR — #316.

Comment 8

[Rémy Hubscher (:natim)]

https://github.com/mozilla-services/loop-server/commit/2f051c6904e192319253119fe29715927cd590eb

r=@leplatrem