Getting to our most recent test build was a bit of a rough ride. I would like to suggest three things:
1) We get back to a regular schedule of doing a build every week. At predictable times so that we all know when it will happen. Additional, Steph suggested that we do builds for both Aurora and TestFlight on Thursday, but then only make the Aurora one available immediately and wait till Monday for the Testflight one. That gives us a little buffer to react to things that absolutely need to be fixed for our external testers. Ideally there is nothing and we can just push the 'Publish' button on Monday. And they still go out on weekly intervals. Specific dates/times can go into the team calendar so that it is very clear when what happens. 2) Run automated tests. We need to get back to a situation where all of our tests are run on Nightly builds and on each and every PR branch. We currently run about 140 (!) unit tests but I am not so sure that includes the UI tests. Which is most likely where we catch regressions. If the UI tests currently don't work on Xcode Server then we need to fix that. If they are simply disabled then we need to turn them back on. 3) Because we are very close to a release, try not to introduce new functionality or refactor big chunks of code. We should be extremely careful with patches that substantially change the internal workings of the app at this point. If you do need to do that, be sure that we have UI/Unit tests that cover all the parts that your patch touches. Either directly or indirectly. If we don't have tests then they need to be written. S.
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
