If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Build with --noftu command line flag in engineering builds?

NEW
Unassigned

Status

Firefox OS
GonkIntegration
4 years ago
2 years ago

People

(Reporter: zac, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [gaia-ui-test])

(Reporter)

Description

4 years ago
Throwing this out to those who use the Engineering builds to see who it might affect.

It would be beneficial to those doing gaia automation to build the engineering builds with the -noftu flag. This would stop the FTU popping up but. 

The FTU can still be loaded via the Developer settings option nestled in the Settings app.
I agree that the FTU is an annoyance on eng builds, which are primarily used for automation.  I don't see any disadvantage to disabling it.
Not having the FTU on eng builds would probably mean less eyes to find bugs.

I don't really mind though, maybe the eyes count is already big enough with keeping it in production builds only.
(Reporter)

Comment 3

4 years ago
We still run the FTU tests in our automation because we can launch the FTU independently so coverage exists.

afaik the manual QA team all us the production builds. I did raise this bug with them for comment but none yet!
Bump

This came up in a discussion about bug 893741. Is this something we can get implemented?
Whiteboard: [gaia-ui-test]
If possible, i'd like to have NO_FTU=1 only for builds used in automation, but not in all eng mode builds. If that's not possible, then, let's do it for all of them...
You need to log in before you can comment on or make changes to this bug.