Closed Bug 1314035 Opened 8 years ago Closed 8 years ago

Change FennecCI scheme to be Fennec and use FirefoxNightly scheme for BB nightly builds

Categories

(Firefox for iOS :: Build & Test, defect, P1)

Other
iOS
defect

Tracking

()

RESOLVED FIXED
Iteration:
1.8

People

(Reporter: sleroux, Assigned: sleroux)

References

Details

(Whiteboard: [MobileAS])

To better support how we produce our builds and run our UI/unit tests on BB, I propose we update the scheme as follows:

1. Remove the FennecCI scheme and simply use Fennec for on commit/merge integrations with unit testing enabled.
2. Change the nightly BB deployment to use the FirefoxNightly scheme which runs unit tests and UI tests.

This will allow us to not bog down BB with UI tests on every push and also allow us to create a FennecNoTests scheme but default to a scheme with tests enabled to allow for safer builds from contributors and streamlined builds for people who want to use the FennecNoTests scheme.
Going to pick this up while I'm working on getting 6.0 to build for beta.
Assignee: nobody → sleroux
Priority: P2 → P1
Iteration: --- → 1.8
As you can see from this list, (https://docs.google.com/spreadsheets/d/1lMPpKKSw2-cNPIxkHO0SPfi55l1HffF5Kdvxbca2wyc/edit#gid=841487504) there are tests that only passes on ipad, or iphone.  For example, DomainAutocompleteTests will fail on ipad, but passes on iphone. 
In order to run tests that only passes on certain devices, we need to create a new scheme for each of them- like FennecCI - Ipad and FennecCI - Iphone and enable applicable tests.  

But if we don't need to test older api, perhaps we can run tests on iphone only. But in that case the tests that fail on them should be disabled.
Status: NEW → ASSIGNED
See Also: → 1313147
Resolved as part of https://bugzilla.mozilla.org/show_bug.cgi?id=1313147
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Just saw your comment :njpark. I've landed the first pass of this bug and removed the FennecCI scheme in favor of just Fennec with tests that are currently working on iPhone. We should probably file a follow up to investigate running the test suite against both iPad and iPhone and figuring out a way to get that going with a single scheme.
You need to log in before you can comment on or make changes to this bug.