On 10/10/12 1:13 AM, Ian Bicking wrote:
OK – so if I understand the objection to testharness isn't anything in
testharness.js itself, but that it's an incomplete solution as it doesn't
define an environment?
That's _my_ primary objection, after looking at it briefly and seeing
how it works in
On Tue, Oct 9, 2012 at 11:41 PM, Boris Zbarsky wrote:
> On 10/10/12 12:23 AM, Ian Bicking wrote:
>
>> Here's how I think you'd write a simple XHR test in both:
>>
>> // SimpleTest aka MochiTest
>> req = new XMLHttpRequest();
>> req.open("GET", "/example.json");
>>
>
> How did example.json get the
On 10/10/12 12:23 AM, Ian Bicking wrote:
Here's how I think you'd write a simple XHR test in both:
// SimpleTest aka MochiTest
req = new XMLHttpRequest();
req.open("GET", "/example.json");
How did example.json get there?
What if you need to test CORS?
With mochitest at this point you're doin
On Tue, Oct 9, 2012 at 8:39 PM, Boris Zbarsky wrote:
> On 10/9/12 6:46 PM, Jonas Sicking wrote:
>
>> On Tue, Oct 9, 2012 at 2:43 AM, Aryeh Gregor wrote:
>>
>>> If it's a pain to write a particular file in testharness.js, it can be
>>> kept as mochitest. In my experience, quite a lot of tests bo
On 10/9/12 6:46 PM, Jonas Sicking wrote:
On Tue, Oct 9, 2012 at 2:43 AM, Aryeh Gregor wrote:
If it's a pain to write a particular file in testharness.js, it can be
kept as mochitest. In my experience, quite a lot of tests boil down
to like ten lines, which would take about three minutes more t
I think the subject says it quite well. Tell me your Snappy status and I'll
talk about it at the platform meeting. Taras might even blog about it. If that
isn't incentive...
https://etherpad.mozilla.org/snappy
Lawrence
___
dev-platform mailing list
de
On Tue, Oct 9, 2012 at 2:43 AM, Aryeh Gregor wrote:
> On Sat, Oct 6, 2012 at 6:25 AM, Jonas Sicking wrote:
>> In general, testharness.js seems to be more optimized for producing a
>> result report which measure how close an implementation is to
>> implementing a feature, than it is optimized for
On 10/08/2012 08:42 AM, thus spoke Justin Lebar:
> Having said that, I don't think it would be hard to write an hg hook
> which comments in the relevant bugs when a push is made to m-i. Maybe
> that would be a reasonable way to get uniformity and immediate
> notification in the bug when a patch i
On 08/10/12 04:14, Boris Zbarsky wrote:
On 10/7/12 4:13 PM, Ehsan Akhgari wrote:
Nice! Can you please share some info on when you can avoid
inheriting from nsISupports and whether we can make the cycle
collector aware of such objects?
Basically, the rules are as follows:
1) You need to eith
I guess 7 digits of precision beyond the decimal point is overkill.
How about we output values rounded to the nearest 1e-6.
Rob
--
“You have heard that it was said, ‘Love your neighbor and hate your enemy.’
But I tell you, love your enemies and pray for those who persecute you,
that you may be c
On Sat, Oct 6, 2012 at 6:25 AM, Jonas Sicking wrote:
> In general, testharness.js seems to be more optimized for producing a
> result report which measure how close an implementation is to
> implementing a feature, than it is optimized for making it easy to
> write tests.
I think it's actually op
11 matches
Mail list logo
