|
Ran
|
Jobs
1
|
Files
28
|
Run time
2s
|
Badge
README BADGES
|
push
travis-ci
<a href="https://github.com/couchbase/moss/commit/<a class=hub.com/couchbase/moss/commit/af650fc974bf5b3f29169671913d713383bc98c0">af650fc97<a href="https://github.com/couchbase/moss/commit/af650fc974bf5b3f29169671913d713383bc98c0">">[4] Formatting the JSON output to look better Changing the JSON dump look to: [ {&quot;K&quot; : &quot;key0&quot;, &quot;V&quot; : &quot;val0&quot;}, {&quot;K&quot; : &quot;key1&quot;, &quot;V&quot; : &quot;val1&quot;}, {&quot;K&quot; : &quot;key2&quot;, &quot;V&quot; : &quot;val2&quot;}, {&quot;K&quot; : &quot;key3&quot;, &quot;V&quot; : &quot;val3&quot;}, {&quot;K&quot; : &quot;key4&quot;, &quot;V&quot; : &quot;val4&quot;}, {&quot;K&quot; : &quot;key5&quot;, &quot;V&quot; : &quot;val5&quot;}, {&quot;K&quot; : &quot;key6&quot;, &quot;V&quot; : &quot;val6&quot;}, {&quot;K&quot; : &quot;key7&quot;, &quot;V&quot; : &quot;val7&quot;}, {&quot;K&quot; : &quot;key8&quot;, &quot;V&quot; : &quot;val8&quot;}, {&quot;K" : "key9", "V" : "val9"} ] This would establish a consistent JSON format to assist future functionality of mossScope - take import (which writes to a moss store) for example, that reads from a JSON file which would need to look in the above format to be validated. Change-Id: I</a><a class="double-link" href="https://github.com/couchbase/moss/commit/<a class="double-link" href="https://github.com/couchbase/moss/commit/ec57f652b9fbae2883947328fb4571a21caff614">ec57f652b</a>">ec57f652b</a><a href="https://github.com/couchbase/moss/commit/af650fc974bf5b3f29169671913d713383bc98c0"> Reviewed-on: http://review.couchbase.org/72370 Reviewed-by: Steve Yen <steve.yen@gmail.com> Tested-by: abhinav dangeti <abhinav@couchbase.com>
2383 of 2893 relevant lines covered (82.37%)
9682.24 hits per line
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 147.1 | 0 |
82.37 |
Travis Job 147.1 |