From df641960fe2670eda103497c0ee3de956e584d9e Mon Sep 17 00:00:00 2001
From: Ger Hobbelt <ger@hobbelt.com>
Date: Fri, 19 Jul 2019 13:32:00 +0200
Subject: [PATCH] tweaking a failing test case: the failure is due to one side
 of the test outputting `"use strict";;` while the other prints `"use
 strict";` -- which is less important an issue than the AST content check,
 hence we move this (failing) test check to the end of the test.

---
 test/mapping.js | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/test/mapping.js b/test/mapping.js
index 7078fd67..279c0505 100644
--- a/test/mapping.js
+++ b/test/mapping.js
@@ -161,11 +161,6 @@ describe("source maps", function() {
         console.error('twoStepResult:', twoStepResult.code)
     fs.writeFileSync('AST4.json', JSON.stringify(useStrictAst, null, 2));        
 
-        assert.strictEqual(
-            oneStepResult.code,
-            twoStepResult.code
-        );
-
         var smc1 = new sourceMap.SourceMapConsumer(oneStepResult.map);
         var smc2 = new sourceMap.SourceMapConsumer(twoStepResult.map);
 
@@ -187,6 +182,11 @@ describe("source maps", function() {
             // source instead of the intermediate source.
             assert.strictEqual(orig2.source, "original.js");
         });
+
+        assert.strictEqual(
+            oneStepResult.code,
+            twoStepResult.code
+        );
     });
 
     it("should work when a child node becomes null", function() {