Closed Bug 924831 Opened 11 years ago Closed 10 years ago

Create plivo account for use with UI tests

Categories

(Firefox OS Graveyard :: Gaia::UI Tests, defect)

Other
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: zcampbell, Assigned: bsilverberg)

References

Details

We need a Plivo account so that we can run tests that receive calls on Jenkins CI.
+ configure Jenkins nodes to use it
Blocks: 924833
Blocks: 924835
Hey all, sorry for being late with this, but I've spoken with bmoss again, and rather than pay for a third-party service, he'd like us to pursue other options that we can manage, ourselves.  Feel free to contact me if you'd more information/context, etc., and again, sorry for the delay in getting back with the update!
While I think that Plivo is pretty cool (as was Twilio), I really think we're asking for trouble with any service like this. If anything goes wrong and the service tries to call the phone after the test has completed (as I've seen happen with Plivo), it will wreak havoc with our test run. So I agree that we should pursue other avenues.
The very first thing I tried was an Android phone with an app on it called 'Tasker' and you can remotely command the phone to make a call, send SMS etc.
I think this would work well and certainly be cheap as we have a phone, SIM and we'd just need to purchase the software, it is limited to only working in MV/USA, difficult to remotely maintain and might be troublesome if more than one test tries to use the phone at once.

Although Plivo might be more expensive initially it has the advantage of speed; we could have this up and running by next week as the tests/API are already written and partially reviewed.

Bob in that situation are you sure that we terminated the call properly (in the tearDown for example)? Looking at their API docs there is also some stuff like "ring timeout" and "hang_up_on_ring"

http://plivo.com/docs/api/call/#outbound

I reckon we should speak to Plivo support about this, I had a look around their site and they seem quite open.
This was discussed by email and the account was created.
There is a pull request in bug Bug 924833 - Re-enable test_receive_call.py

Bob can you add more info or close this please
Flags: needinfo?(bob.silverberg)
An account has been created for the email address webqa@mozilla.org at Plivo and the credentials for that account have been included in a pull request [1] that is waiting to be merged.

The only thing outstanding after that is to create a mechanism to make payments to add to the account balance when it starts to get low.

Stephen, whom should I ask about that?

[1] https://github.com/mozilla/webqa-credentials/pull/109
Flags: needinfo?(bob.silverberg) → needinfo?(stephen.donner)
(In reply to Bob Silverberg [:bsilverberg] from comment #6)
> The only thing outstanding after that is to create a mechanism to make
> payments to add to the account balance when it starts to get low.
> 
> Stephen, whom should I ask about that?

Not sure about creating a mechanism (would that be through an API of theirs?); or would this just be a process?  If the latter, we might be able to get the Service Desk folks to help us manage this account.  They're already doing so with our ActiveSync/Hotmail accounts, and AT&T/T-Mobile SIM cards.  Jennifer Hayashi would be a good choice to follow-up with.
Flags: needinfo?(stephen.donner)
Bob are you happy with this bug to be closed? Or want to split out the API stuff into a separate task?
Flags: needinfo?(bob.silverberg)
Zac, we still haven't worked out exactly how we're going to 'top up' the account when needed, which looks like it's on me to figure out, so we'd better leave this open for now.
As an update, I have, as suggested by Stephen, sent an email to Jennifer Hayashi asking about a mechanism to top up the Plivo account.
Assignee: stephen.donner → bob.silverberg
Flags: needinfo?(bob.silverberg)
The final decision is that stephend will just top up the account as needed and will expense it. We can close this bug.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.