On Mon, Jul 22, 2013 at 7:27 AM, Lucas Rocha <[email protected]> wrote:
> ----- 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. > Do you mean getting tests set up running locally? This hasn't proved to be too difficult anymore, but I agree that I wouldn't want a new person spending their time just trying to set that up if they don't already have that set up. However, I would hope everyone on our team would be able to run a robocop test locally! > 2. The test infra fixes for fig are likely hard to split. So, again, it > would probably be only one person stuck with it. > I did the leg work to get most of the blocking issues sorted out in bug 880060. If you take a look at bug 895673, you'll see a list of disabled tests that just need to be either fixed or removed, and doing those one by one should be pretty easy work to split up. My goal is for there to *not* be one person stuck with it. I just started an etherpad to help us keep track of the state of testing, so that it's easier to communicate about work going on in parallel: https://etherpad.mozilla.org/fig-testing 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 understand that hacking on tests isn't as glamorous as remaining feature work, but merging will be easier (and happen sooner) if it isn't an afterthought. We're definitely at the point now where other people can start helping out, especially when it comes to testing the new features that they've been working on. Margaret
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
