Hi Jan! Idea is really good one - this is the way I found that 2.0 doesn't support multipart/* Accept against document resources. I think there is nothing to feedback, need just run it and sort the positive fails from negative ones.
-- ,,,^..^,,, On Wed, Apr 1, 2015 at 11:26 PM, Jan Lehnardt <[email protected]> wrote: > Heya, > > bumping this as I’d love to get some feedback on the idea :) > > Thanks! > Jan > -- > >> On 18 Mar 2015, at 22:24, Jan Lehnardt <[email protected]> wrote: >> >> Hi all, >> >> I’m concerned about people upgrading from 1.x to 2.0 and finding that >> a number of small things are subtly broken. >> >> I propose we figure out how to run the JavaScript test suite against >> the clustered port in master, as they are a decent approximation of >> what 1.x clients expect. >> >> There will be a few things that need disabling (tests for _config >> e.g.) and some need adjusting (expecting the seq_id to be a number), >> but overall, I think this is not a bad task. >> >> I know the JavaScript tests aren’t well liked here, but we’ve spent >> quite some time putting a lot of CouchDB API knowledge into them >> and I don’t want to miss an opportunity to make upgrades to 2.0 as >> seamless as possible. >> >> What do you think? >> >> Best >> Jan >> -- >> Professional Support for Apache CouchDB: >> http://www.neighbourhood.ie/couchdb-support/ >> > > -- > Professional Support for Apache CouchDB: > http://www.neighbourhood.ie/couchdb-support/ >
