https://blog.gof.me/enContents © 2019 <a href="mailto:godfryd@gmail.com">Godfryd</a> Mon, 29 Apr 2019 06:40:47 GMTNikola (getnikola.com)http://blogs.law.harvard.edu/tech/rsshttps://blog.gof.me/posts/checking-couchdb/Godfryd<div><p></p><p>I'm working on presentation for winter <a href="http://zimowisko.linux.gda.pl/">get-together</a> of TriCity Linux User Group. This will be about schema-less database <a href="https://blog.gof.me/posts/checking-couchdb/couchdb.apache.org">CouchDB</a>. I don't to do simple introductory presentation as such there are plenty on internet. I'd like to check if particular problem can be solved using CouchDB.</p> <p><a href="https://blog.gof.me/posts/checking-couchdb/">Read more…</a> (3 min remaining to read)</p></div>databasereportingSoftwaretestinghttps://blog.gof.me/posts/checking-couchdb/Wed, 06 Jan 2010 07:55:44 GMThttps://blog.gof.me/posts/test-results-reporting/Godfryd<div><p></p><p>Generally it is quite simple. Run tests. Count the number of all tests and failed tests and thats it. In most books about Continuous Integration and testing it is written that when some test fails the build is broken. Then just fix it to have still 100% passes and go on. In real projects it is not so simple.</p> <p><a href="https://blog.gof.me/posts/test-results-reporting/">Read more…</a> (6 min remaining to read)</p></div>reportingSoftwaretestinghttps://blog.gof.me/posts/test-results-reporting/Sun, 21 Jun 2009 08:45:52 GMT