Issue 5760 - Use relative require paths

qunit/tests/filterValidation.js

 "use strict";
 
 {
   const {parseFilter, parseFilters} = require("filterValidation");

[kzar, 2018/04/05 11:14:57]

What about this one?

[Jon Sonesen, 2018/04/05 23:01:20]

Since this file is names filterValidation as well, I guess I though I didn't
need to, my bad.

   const {BlockingFilter,
          ElemHideFilter,
-         CommentFilter} = require("filterClasses");
+         CommentFilter} = require("../../adblockpluscore/lib/filterClasses");
 
   QUnit.module("Filter validation");
 
   test("Detecting invalid filters", () =>
   {
     equal(parseFilter("||example.com^$unknown").error.type, "invalid-filter",
           "unknown option");
     equal(parseFilter("[foobar]").error.type, "unexpected-filter-list-header",
           "filter list header");
     equal(parseFilter("##[foo").error.type, "invalid-css-selector",
@@ skipping 46 matching lines @@
     ok(result.filters[0] instanceof BlockingFilter, "1st filter is blocking");
     equal(result.filters[0].text, "||example.com^", "1st filter text matches");
 
     ok(result.filters[1] instanceof ElemHideFilter, "2nd filter is elemhide");
     equal(result.filters[1].text, "###foobar", "2nd filter text matches");
 
     ok(result.filters[2] instanceof CommentFilter, "3rd filter is comment");
     equal(result.filters[2].text, "! foo bar", "3rd filter text matches");
   });
 }