[javascript] Removing comment as we are opening a browser per test

diemol · diemol · commit 8215a1e0c1ec · 2022-04-08T11:17:38.000+02:00
It is not ideal to open a browser per test but this seems
to make tests in Chrome run more stable.
diff --git a/javascript/node/selenium-webdriver/test/actions_test.js b/javascript/node/selenium-webdriver/test/actions_test.js
@@ -18,7 +18,6 @@
 'use strict'
 
 const assert = require('assert')
-const error = require('../lib/error')
 const fileServer = require('../lib/test/fileserver')
 const { ignore, Pages, suite } = require('../lib/test')
 const { Key, Origin } = require('../lib/input')
@@ -107,12 +106,6 @@ suite(function (env) {
         assert.strictEqual(await box.getAttribute('class'), 'blue')
       })
 
-    // For some reason for Chrome 75 we need to wrap this test in an extra
-    // describe for the afterEach hook above to properly clear action sequences.
-    // This appears to be a quirk of the timing around mocha tests and not
-    // necessarily a bug in the chromedriver.
-    // TODO(jleyba): dig into this more so we can remove this hack.
-    // describe('dragAndDrop()', function () {
     it('dragAndDrop()', async function () {
       await driver.get(fileServer.whereIs('/data/actions/drag.html'))
 
@@ -130,7 +123,6 @@ suite(function (env) {
       assert.strictEqual(await slide.getCssValue('left'), '206px')
       assert.strictEqual(await slide.getCssValue('top'), '1px')
     })
-    //  })
 
     it('move()', async function () {
       await driver.get(fileServer.whereIs('/data/actions/drag.html'))
