Hey Margaret, ----- Original Message ----- > I also think we should take this opportunity to hack on tests, since creating > tests for the new UI feels like a bigger task than a "loose end". In > addition to trying to re-enable the failing tests, we should also make a > plan for how to test new UI, since some of those disabled tests should > probably just be removed now that the UI is different. I'll make a follow-up > post to the thread about testing on fig to start to hash out some of the > details!
The reasons why haven't included test infra work in the hackathon are: 1. Test infra work tends to be very time-consuming. It's likely that whoever worked on this would get "stuck" with it for most of the hackathon. 2. The test infra fixes for fig are likely hard to split. So, again, it would probably be only one person stuck with it. However, if you really want to focus on this during the hackathon, feel free to do so :-) As you said, this is something we'll have to do before the merge anyway. The rationale behind the list of bugs we proposed for the hackathon is that we'd be more effective if we focus on tackling the missing pieces of the new about:home UI (more parallel work, more self-contained, etc). I hope that clarifies our intent. Cheers! --lucasr _______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
