Le 20/11/2013 02:40, Zac Campbell a écrit :
> It strikes me that with devs writing tests there's a huge potential for 
> gaming your system of only landing tests with bugs and/or patches.
>
> Why would a dev want to write a rigid and reliable test? It delays the 
> feature/bug fix, it's harder and it might have to be maintained in the future 
> if it fails. We all know it's easy to write a test that's more likely to stay 
> green over time.
>
> The reviewer on the other hand can take the green "OK to merge" of Travis far 
> to literally and not thoroughly review the tests, particularly when under 
> some time pressure.

Well, I think we can rely on reliable engineers to write and review tests :)

>
> With a 2nd party writing tests and defining quality there's a balance to the 
> equation, like the opposing sides of the stock market that, in the long term, 
> keep things in equilibrium.
>


I don't really understand why both frameworks are in opposition.

*  the JS framework is good for developers to write tests
*  the Python framework is good for QA to write tests

When I look at the Gaia repository, I see some apps have JS-based tests,
and that's good. But a lot of apps don't have any (lack of time to write
some or learn, lack of "first test" in the app) and we still need some
integration tests, right? That's where zac and his team are valuable.

In the european timezone they've been very available to help.

As for red trees because a UI Test has not been updated, that should
have been caught at pull request time anyway.

In the end, I'd really prefer everyone to use the JS-based framework. As
everybody said, in the end, both frameworks are similar, and what's
difficult is to write a good UI Test. What I dislike with the
Python-based framework is that you end up writing both JS and Python,
this is not natural. But as long as someone maintains the Python-based
tests I won't say much.

-- 
Julien

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g

Reply via email to