You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unfortunately, it looks like your tests are quite tightly bound to wording in old versions of couchdb though, so while it was trivial to fix this, running the tests against the latest couchdb shows a lot of problems because of some changed error messages:
[info] User interface
[error] x Get info about the DB instance
[error] '-\/(upickle.Invalid$Data: Key Missing: uuid (data: {
[error] "couchdb": "Welcome",
[error] "version": "2.0.0",
[error] "vendor": {
[error] "name": "The Apache Software Foundation"
[error] }
[error] }))' is not \/- (CouchDbSpecification.scala:47)
[info]
[error] x Create and query 2 DBs
[error] 'Database does not exist.' is not equal to 'missing' [CouchDbSpec.scala:42]
[error] 'Database does not exist.' is not equal to 'missing' [CouchDbSpec.scala:42] (CouchDbSpec.scala:42)
[error] Actual: Database does not exist.
[error] Expected: missing
Largely the errors are to do with error messages changing, so I'd suggest you try to eliminate some of the dependence on precise wording (usually a good idea for any test to avoid relying on information aimed for humans to read), however it looks like some other API details may have changed, so the library probably needs an update to account for a couple of changes in newer couchdb versions.
[error] x fail if one or more elements is missing a Rev
[error] '-\/(upickle.Invalid$Data: Key Missing: offset (data: {
...
Copied this from #76 as I discovered it while attempting to resolve that issue.
The text was updated successfully, but these errors were encountered:
It looks like #80 may be related to this (though it looks like someone's attempted to overhaul all the licensing at the same time so it's probably not very helpful)
Unfortunately, it looks like your tests are quite tightly bound to wording in old versions of couchdb though, so while it was trivial to fix this, running the tests against the latest couchdb shows a lot of problems because of some changed error messages:
Largely the errors are to do with error messages changing, so I'd suggest you try to eliminate some of the dependence on precise wording (usually a good idea for any test to avoid relying on information aimed for humans to read), however it looks like some other API details may have changed, so the library probably needs an update to account for a couple of changes in newer couchdb versions.
Copied this from #76 as I discovered it while attempting to resolve that issue.
The text was updated successfully, but these errors were encountered: