search

ole-vi / BeLL-Apps

This is the third iteration of the BeLL software. It's a Backbone.js app that caches itself in the browser that is backed by CouchDB when a server is available and PouchDB in the browser when a server is not available. Initial support for PDFs is currently implemented, support for Videos and single HTML5 Apps coming next. Tracking bugs and new features in the Wiki at the moment.
1 stars 12 forks source link

pure python test to check what is in couch #60

Open dogi opened 7 years ago

dogi commented 7 years ago

suggest using pycouch something similar to curl ;P and check against what we think should be there ...

anyhow once we know how to do that for travis think this test will simple and always the same, but in local testing it will give us the ability to fix from former tests ...

@dogi s hope is to fix local couchdb of ole--vagrant-travis before the tests run, so that in a 2nd step login test has no optional out come anymore

waryhermit commented 7 years ago

@dogi This gives me another idea on how to approach this through codeceptjs. There are hooks available for before all tests run, could load the config there. Might be able to load cookies there too.

waryhermit commented 7 years ago

To clarify there are sort of two issues here. We want to make the travis and local tests to face the same UI. To do this we want to make the configurations screen not appear, and we want to leave no mess or clean up any mess in the couch DB each time the tests are run.

waryhermit commented 7 years ago

@dogi Accessing couch-db within the testing framework does seems pretty doable. I wonder how much cleaning we should do, and how much we need to leave to the test writers to decide for them selves. I can imagine in some situations it might be annoying for all the databases to be wiped each testing session. You might want to go back and look at stuff to get an understanding of how your test malfunctioned.

Any thoughts?

dogi commented 7 years ago

@waryhermit this seems like one of the ways to approach this issue ;)

an other would be after install by checksum or other meaning to check the status of certain DBs and compare that with the result of an other runs of the same check with difference it was for example done after one of our tests