On 2/5/2016 3:48 PM, Joe Mistachkin wrote:
Ross Berteig wrote:
The simple answer is to always name the fossil to test as fossil.exe on
Windows when running tester.tcl. A slightly more robust answer would be
include some code in tester.tcl that makes sure the ".exe" got put there
if appropriate.
Thanks for the report. Fixed on trunk.
Just merged that into my branch, works like a charm, thanks.
A recent change added two commands to TH1 and broke the test
th1-info-commands. I've fixed it and made the test more robust in my branch.
At this point, my branch passes all tests aside from the known bugs, and
has been freshly merged from trunk. The merge back to trunk should be
nearly risk-free and painless.
I've got test coverage of all the prominent features of the fossil json
command, and want to shift my attention to increasing the code coverage
of the rest of the test suite.
So it seems like a good point to suggest integrating the
rberteig-json-test branch into trunk. Does anyone want to review that
further or should I just boldly do the merge myself?
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
_______________________________________________
fossil-dev mailing list
fossil-dev@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
