test: projects store tiemout fix

Author: jakobrosenberg

test/suite/integration/probs.config.js

@@ -2,7 +2,7 @@ const vscode = require("vscode");
 const { resetFixture } = require("../../utils");
 
 const workspaceDir = process.env.fixturePath;
-const PROJECT_STORE_TIMEOUT = 3000;
+const PROJECT_STORE_TIMEOUT = 10000;
 
 /**
  * @param {Device} device

test/suite/integration/projects.test.js

@@ -12,22 +12,19 @@ test("can find 0 projects and 1 workspace", () => {
 test("can create project", async () => {
   await pymakr.commands.createProject(vscode.Uri.parse(projectPath1), { name: "my project" });
   assert(existsSync(projectPath1));
-
   test("new project has pymakr.conf", () => {
     const configFile = readFileSync(`${projectPath1}/pymakr.conf`, "utf8");
     const config = JSON.parse(configFile);
     assert.equal(config.name, "my project");
   });
-
   test("projects store updates on new project", () => {
     return new Promise((resolve, reject) => {
-      setTimeout(reject, PROJECT_STORE_TIMEOUT);
+      setTimeout(() => reject("project store timed out"), PROJECT_STORE_TIMEOUT);
       pymakr.projectsStore.next(resolve);
     });
   });
-
   test("new project shows up in vscode", async () => {
     assert.equal(pymakr.projectsStore.get().length, 1);
-    assert.equal(pymakr.projectsStore.get()[0].name, 'my project')
+    assert.equal(pymakr.projectsStore.get()[0].name, "my project");
   });
 });