I've finished filling in context on the various bugs, as promised. I'm
sure there are holes, but I think I've captured the majority of the
context behind the various decisions in the bugs.
I fat-fingered a few of the bug numbers the first time around, here's
the original post with corrections:
On 2/28/14, 1:57 PM, Dan Mosedale wrote:
Stand-alone and in-browser unit-testing framework (bug 976789)
* mocha & chai, already used by b2g for gaia as well as the loop server
* good at structuring large suites in maintainable ways
* fast and very efficient toolchains in and around these tools
* after talking to folks on the a-team, it appears that it should be
straightforward to integrate with the Tbpl infrastructure
The above bug number is wrong. That should actually read (bug 975127,
bug 976133).
CSS toolkit for standalone and in-browser code: (bug 976854 and bug
976857)
* None; easy to mix-in later if we want something later
MVC infrastructure (bug 975548)
* Well-understood/tested code structuring for moving fast
* Many B2G apps have rolled their own, and it hasn't been easy.
* Backbone + dependencies optimized for mobile (zepto/underscore) CSS
toolkit for standalone and in-browser code
Call Notification (bug 976789)
* SimplePush: as far as we can see, this is the only easily-scalable
solution that exists
Client-driven end-to-end testing framework for both browser and
standalone (bug 976134, bug 976114, bug 972026)
* Marionette generally
* mix-in Steeplechase for tests that need NAT traversal
** will need work from Ted, which he sounds open to doing
Bug 972026 doesn't actually belong to this set.
Dan
_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media
