get rid of requirement to have canisters listed for fuzz testing, get…

… them from the dfx.json only, update cuzz
demergent-labs · Nov 25, 2024 · c42db24 · c42db24
1 parent 5b6c0ed
commit c42db24
Show file tree

Hide file tree

Showing 4 changed files with 5 additions and 8 deletions.
diff --git a/canister_templates/stable.wasm b/canister_templates/stable.wasm
diff --git a/package-lock.json b/package-lock.json
diff --git a/package.json b/package.json
@@ -37,7 +37,7 @@
         "class-transformer": "^0.5.1",
         "class-validator": "^0.14.1",
         "crypto-browserify": "^3.12.0",
-        "cuzz": "github:demergent-labs/cuzz#e43d85edf09e84b03411980a8b11086cd1c55a14",
+        "cuzz": "github:demergent-labs/cuzz#45c03fd9d503783480ddc36e86679507be76b39b",
         "deep-is": "^0.1.4",
         "esbuild": "^0.23.0",
         "esbuild-plugin-tsc": "^0.4.0",

diff --git a/test/index.ts b/test/index.ts
@@ -64,10 +64,7 @@ export function runTests(
         });
     }
 
-    // TODO we should work on what the UI looks like if there are multiple of these things running
-    if (shouldFuzz && canisterNames !== undefined) {
-        // TODO right now we just test the first canister...that might be good enough for now?
-        // TODO because I feel that the first canister will generally call the other canisters
+    if (shouldFuzz === true) {
         describe(`fuzz`, () => {
             it('runs fuzz tests for all canisters', () => {
                 // execSyncPretty(`cuzz`, 'inherit');