Closed Bug 1042141 Opened 11 years ago Closed 10 years ago

Investigate tests for quick verification of MSISDN-Gateway deploys to Production

Categories

(Cloud Services Graveyard :: MobileID, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: jbonacci, Assigned: rhubscher)

References

Details

(Whiteboard: [qa+])

QA has a starting point here: https://github.com/natim/msisdn-verifier-client Some notes from :natim 12:34 <@jbonacci> natim did you say that you have a tool for checking MSISDN-Gateway production 12:38 <@natim> Yes 12:38 <@natim> jbonacci: 12:38 <@natim> You can clone https://github.com/natim/msisdn-verifier-client 12:39 <@natim> And then modify js/js/client_request_helper.js to set the production url (or any environment you wanna try) 12:39 <@natim> Then you serve the webapp 12:39 <@natim> python -m SimpleHTTPServer 8000 12:40 <@natim> Then you can connect http://localhost:8000/ to verify one or the other flow 12:40 <@natim> note that you will need your country Mobile Country Code MCC which is for the US 12:41 <@natim> 310 12:41 <@natim> Your msisdn number is +1 and your local number 12:41 <@natim> For me it is +33683913987 for instance 12:41 <@natim> If you enter MSISDN + MCC you will get the MT flow 12:42 <@natim> If you enter just the MCC you will start the MOMT flow 12:42 <@natim> After than you will probably get sick of all the copy paste but you know... 12:44 <@natim> For the MOMT flow you will have to send "SMS code" (where code is the one given by the application to the moVerifier number 12:44 <@natim> Then you will get back a MT SMS that you will be able to verify Please follow-up with :natim to come up with some steps for using this repo to perform quick verifications of Prod deploys. Thanks.
Whiteboard: [qa+]
I will try to spend some time on this later today (Wed 2014-07-23).
Component: Server → MobileID
Product: Loop → Mozilla Services
QA Contact: jbonacci
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Assignee: nobody → rhubscher
Awesome thanks. How does this differ from the use of: http://mozilla-services.github.io/msisdn-verifier-client from https://github.com/mozilla-services/msisdn-verifier-client ? CLI vs. webapp but they both accomplish the same thing?
Both tools are made to try out the MSISDN-Gateway server. Yes they both accomplish the same thing, after it is just a matter of taste to use one or the other.
So, on a local install, the tool is here: ../msisdn-gateway/tools/roundtrip Looks like the first thing to do is a 'make install'. Here is a pastebin of my 'make install' https://jbonacci.pastebin.mozilla.org/6060746 Trying this against Stage just for the heck of it: python roundTrip.py -H https://msisdn.stage.mozaws.net -c 310 This results in an error: Traceback (most recent call last): File "./roundTrip.py", line 7, in <module> from docopt import docopt ImportError: No module named docopt Same for Prod (just checking): python roundTrip.py -H https://msisdn.stage.mozaws.net -c 310 Same for just 'python roundTrip.py' So everything looks ok to me. Why the ImportError?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
In addition, I can not get the webapp to work for msisdn Stage and maybe it's not supposed to work. I can not get the webapp to work for Prod either: My 'MSISDN Server' value is https://msisdn.services.mozilla.com My 'MSISDN' value is my FxOS phone: 6509468720 (I also tried 16509468720 and +16509468720) My 'MCC' value is 315 With the Prod server, I do get the message that an SMS will be sent to my phone, but I never receive it. So, I can't even tell if it was sent...
I should also mention that I was using this webapp, specifically: http://mozilla-services.github.io/msisdn-verifier-client/
The MSISDN number should always be +16509468720 For the roundTrip you should use .venv/bin/python roundTrip.py <with_args> or activate the venv first: source .venv/bin/activate python roundTrip.py <with_args> If you are using it on stage, then you need to check the SMS with omxne: http://omxen.dev.mozaws.net/receive?to=16509468720
Ah, some updates overnight. OK thanks! I will have another look today. /me wonders if Loop must be installed on the phone. I recently flashed my phone back to 2.0, which does not have Loop installed by default. I will address this as well...
Those updates being this commit: https://github.com/mozilla-services/msisdn-gateway/commit/68a23c00d0bbdc6ae66fff4ca8df1d694fe19b16 Also adding bug 1045966 as a dependency since it has moar better changes...
Depends on: 1045966
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → FIXED
Yea, the tool in GitHub replaces all this. I will file issues there as I find them...
Status: RESOLVED → VERIFIED
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.