diff options
Diffstat (limited to 'plugins/af_readability/vendor/fivefilters/readability.php/test/test-pages/001/expected.html')
| -rw-r--r-- | plugins/af_readability/vendor/fivefilters/readability.php/test/test-pages/001/expected.html | 18 |
1 files changed, 11 insertions, 7 deletions
diff --git a/plugins/af_readability/vendor/fivefilters/readability.php/test/test-pages/001/expected.html b/plugins/af_readability/vendor/fivefilters/readability.php/test/test-pages/001/expected.html index e05810ff7..0998436c5 100644 --- a/plugins/af_readability/vendor/fivefilters/readability.php/test/test-pages/001/expected.html +++ b/plugins/af_readability/vendor/fivefilters/readability.php/test/test-pages/001/expected.html @@ -1,4 +1,5 @@ -<section><p><strong>So finally you're <a href="http://fakehost/code/2013/testing-frontend-javascript-code-using-mocha-chai-and-sinon/">testing your frontend JavaScript code</a>? Great! The more you +<section> + <p><strong>So finally you're <a href="http://fakehost/code/2013/testing-frontend-javascript-code-using-mocha-chai-and-sinon/">testing your frontend JavaScript code</a>? Great! The more you write tests, the more confident you are with your code… but how much precisely? That's where <a href="http://en.wikipedia.org/wiki/Code_coverage">code coverage</a> might help.</strong> @@ -15,9 +16,9 @@ help.</strong> actually works…</p> <blockquote> <p>Drinking game for web devs: - <br></br>(1) Think of a noun - <br></br>(2) Google "<noun>.js" - <br></br>(3) If a library with that name exists - drink</p>— Shay Friedman (@ironshay) + <br>(1) Think of a noun + <br>(2) Google "<noun>.js" + <br>(3) If a library with that name exists - drink</p>— Shay Friedman (@ironshay) <a href="https://twitter.com/ironshay/statuses/370525864523743232">August 22, 2013</a> </blockquote> <p><strong><a href="http://blanketjs.org/">Blanket.js</a></strong> is an <em>easy to install, easy to configure, @@ -105,13 +106,16 @@ describe("Cow", function() { </code></pre> <p><strong>Notes</strong>:</p> - <ul><li>Notice the <code>data-cover</code> attribute we added to the script tag + <ul> + <li>Notice the <code>data-cover</code> attribute we added to the script tag loading the source of our library;</li> <li>The HTML test file <em>must</em> be served over HTTP for the adapter to be loaded.</li> - </ul><p>Running the tests now gives us something like this:</p> + </ul> + <p>Running the tests now gives us something like this:</p> <p> - <img alt="screenshot" src="http://fakehost/static/code/2013/blanket-coverage.png"></img></p> + <img alt="screenshot" src="http://fakehost/static/code/2013/blanket-coverage.png"> + </p> <p>As you can see, the report at the bottom highlights that we haven't actually tested the case where an error is raised in case a target name is missing. We've been informed of that, nothing more, nothing less. We simply know |