couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Noah Slater <>
Subject Re: fix testing in next major release
Date Sun, 02 Jun 2013 10:43:38 GMT
Big +1 from me.

One of the ideas I had recently was to run each test 1,000 times (or
whatever) and calculate the probability of it failing. That should enable
us to prioritise the most brittle tests.

But it seems like you have a much more radical idea in mind. +1 for being

On 29 May 2013 14:35, Benoit Chesneau <> wrote:

> I would like to start to rewrite all of our tests to make them really
> relianle.
> The problems that I want to fix are the following:
> - try to remove most of the sleep w e have around
> - remove JS tests when it's about testing the HTTP API. There are
> actually no reason to test the HTTP API by faking a browser like we do
> actually when we could test expected response against requests. The JS
> tests should only be used eventually to test the the _change API or
> CORS features, basically any browser features. But we are still doing
> it wrong right now.
> - Etap is not maintained anymore. I think we should move to eunit and
> other standards things.
> Thoughts?
> - benoit


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message