Force failure in tests to check the reporting works properly

Signed-off-by: Jesús Benito Calzada <bjesus@vmware.com>
beni0888 · Oct 11, 2022 · d405e1a · d405e1a
1 parent 8a897e1
commit d405e1a
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/integration/tests/carvel/04-default-deployment.spec.js b/integration/tests/carvel/04-default-deployment.spec.js
@@ -40,7 +40,7 @@ test("Deploys package with default values in main cluster", async ({ page }) =>
   await page.waitForSelector("css=.application-status-pie-chart-number >> text=3", {
     timeout: utils.getDeploymentTimeout(),
   });
-  await page.waitForSelector("css=.application-status-pie-chart-title >> text=Ready", {
+  await page.waitForSelector("css=.application-status-pie-chart-title >> text=ReadyFoo", {
     timeout: utils.getDeploymentTimeout(),
   });
 

diff --git a/integration/tests/main/00-log-in.spec.js b/integration/tests/main/00-log-in.spec.js
@@ -12,6 +12,6 @@ test.describe("Log in", () => {
     // like `process.env.VIEW_USER` and `process.env.VIEW_PASSWORD` or similar
     await k.doLogin("kubeapps-user@example.com", "password", process.env.VIEW_TOKEN);
 
-    await page.waitForSelector('css=h1 >> text="Applications"');
+    await page.waitForSelector('css=h1 >> text="ApplicationsFoo"');
   });
 });
diff --git a/integration/tests/operators/06-operator-deployment.spec.js b/integration/tests/operators/06-operator-deployment.spec.js
@@ -14,7 +14,7 @@ test("Deploys an Operator", async ({ page }) => {
 
   // Go to operators page
   await page.goto(utils.getUrl("/#/c/default/ns/kubeapps/operators"));
-  await page.waitForSelector('h1:has-text("Operators")');
+  await page.waitForSelector('h1:has-text("OperatorsFoo")');
   await page.waitForFunction('document.querySelector("cds-progress-circle") === null');
 
   // Select operator to deploy