Compare JS output files against file instead of hardcoded set

A difference is not obvious when two sets are compared: there might be just one different element, but sets would be printed in one line in iteration order (which is non-fixed for hashsets). Also the properties: EXPECTED_JS_FILES_IN_OUTPUT_FOR_STDLIB_ONLY, EXPECTED_JS_FILES_IN_OUTPUT_FOR_MODULE_STDLIB_ONLY, EXPECTED_JS_FILES_IN_OUTPUT_NO_COPY, EXPECTED_JS_FILES_IN_OUTPUT_WITH_ADDITIONAL_LIB_AND_DEFAULT_DIR, EXPECTED_JS_FILES_IN_OUTPUT_WITH_ADDITIONAL_LIB_AND_CUSTOM_DIR are hard to distinguish in code and are not convenient to edit.
2018-02-21 21:54:22 +03:00
parent 9fdd34ce6e
commit 7881a305d9
9 changed files with 155 additions and 68 deletions
@@ -0,0 +1,20 @@
+kotlinProject/
+  custom/
+    META-INF-ex/
+      file2.js
+    dir/
+      file1.js
+    file0.js
+    jslib-example.js
+    jslib-example.meta.js
+    kotlin-experimental.js
+    kotlin-experimental.meta.js
+    kotlin.js
+    kotlin.meta.js
+    res0.js
+    resdir/
+      res1.js
+  kotlinProject/
+    root-package.kjsm
+  kotlinProject.js
+  kotlinProject.meta.js