From 26dc6f0ec290d2e5a499372ab0abd5fdbbf57448 Mon Sep 17 00:00:00 2001 From: Andres Rey Date: Fri, 23 Dec 2016 11:30:32 -0300 Subject: Updated the fake url for the test case and corrected more expected htmls --- test/test-pages/001/expected.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'test/test-pages/001') diff --git a/test/test-pages/001/expected.html b/test/test-pages/001/expected.html index bf3075c..c101aec 100644 --- a/test/test-pages/001/expected.html +++ b/test/test-pages/001/expected.html @@ -1,4 +1,4 @@ -

So finally you're testing your frontend JavaScript code? Great! The more you +

So finally you're testing your frontend JavaScript code? Great! The more you write tests, the more confident you are with your codeā€¦ but how much precisely? That's where code coverage might help. @@ -34,7 +34,7 @@ with nodejs. mocha-blanket.js

As an example, let's reuse the silly Cow example we used - in a previous episode:

+ in a previous episode:

// cow.js
 (function(exports) {
   "use strict";
@@ -111,7 +111,7 @@ describe("Cow", function() {
                                 be loaded.
                         

Running the tests now gives us something like this:

- screenshot

+ screenshot

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 -- cgit v1.2.3