I agree that the key thing we want to check daily is whether then account creation / sign in flow works properly. Rest of the test suite can be executed periodically by myself or whoever wants to verify the status manually.
So what’s the process for getting the agreement? is there a list of people that I should contact? Thanks! NP On May 12, 2014, at 4:27 PM, Jason Smith <[email protected]> wrote: > To add smoketests to the smoketest suite, you would need to request an > addition to the smoketest suite on qa-b2g & see if we get agreement that the > test case should be ran daily. If there's agreement, then we'll update the > spreadsheet & associated MozTrap test suite for smoketests to include that > new smoketests. > > Note - the general phone smoketests should only focus on testable areas that > if broken, tell us that a critical feature of the phone is broken. On that > regard, I'd expect that there would only be one test case for Firefox > Accounts in the smoketest suite (probably a sign in flow) that would replace > the old persona trusted UI test case. > > ----- Original Message ----- >> From: "No-Jun Park" <[email protected]> >> To: [email protected] >> Cc: [email protected], "Tony Chung" <[email protected]> >> Sent: Monday, May 12, 2014 8:31:33 AM >> Subject: Adding manual Firefox Test Cases >> >> Hi Jason, I have created some basic test cases that covers the Firefox >> account features from the client perspective, and they are here: >> >> https://moztrap.mozilla.org/manage/cases/?filter-suite=618 >> >> And I picked 4 of them as smoke tests, and created another suite here: >> >> https://moztrap.mozilla.org/manage/cases/?filter-suite=656 >> >> Currently they are in draft state. Richard reviewed it, but also would >> welcome other feedbacks as well. >> >> I was wondering, what are the steps to be taken so the smoke test suite can >> be tested by contractors on a regular basis? At the moment, developers are >> still working on implementing some of the features/bugfixes (but majority of >> the features are done and in master branch), and we file bugs against Bug >> 996101 for sorting purpose. >> >> cc’ing fxa team for more input. >> >> Thanks, >> >> No-Jun _______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
