Self healing AI capability doesn't repeat waitForVisible/waitForElement step healing for more than 1 BDD scenario (test)

Aperta
#4,527 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
javascript, nodejs, playwright
Ambito
ai, testing-qa

Direzione di ricerca

Start with the heal.addRecipe('ai', ...) configuration and the ai.healFailedStep entry point shown in the issue. Reproduce the two-scenario BDD case with waitForVisible or waitForElement on the listed CodeceptJS, Node.js, and Playwright versions, then trace why healing runs only for the first scenario. Done means the second scenario also invokes self-healing and its logs show the healing attempt.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

stale
What are you trying to achieve?

We would like to use self healing AI capability https://codecept.io/ai/#self-healing-tests on CI with non default steps (waitForVisible/waitForElement) for more then 1 BDD scenario (test)

@test
Feature: Check that self healing works for more then 1 scenario

    Scenario: Self-healing test 1
        Given The tests is logged into Application
        
    Scenario: Self-healing test 2
        Given The tests is logged into Application
What do you get instead?

Self-healing is being invoked for the first scenario (test) on waitForVisible step and doesn't for the second on the same step.

  • logs from 1st scenario:
    [1]  Error (Non-Terminated) | Error: element ({id: usernameee}) still not present on page after 15 sec
locator.waitFor: Timeout 15000ms exceeded.
Call log:
  - waiting for locator('#usernameee').first()
 | async (err) => { isHealing = true if (caughtError ...
  codeceptjs:heal Self-healing started I.waitForElement({"id":"usernameee"}, 15) +0ms
      › Trying to heal I.waitForElement({"id":"usernameee"}, 15) step
  • logs from 2nd scenario:
    [3]  Error (Non-Terminated) | Error: element ({id: usernameee}) still not present on page after 15 sec
locator.waitFor: Timeout 15000ms exceeded.
Call log:
  - waiting for locator('#usernameee').first()
 | (err) => { step.status = 'failed'; step.endTime = ...
    [3] Error | Error: element ({id: usernameee}) still not present on page after 15 sec
locator.waitFor: Timeout 15000ms exceeded.
Call log:
  - waiting for locator('#usernameee').first()
 undefined...
    [3] <teardown>  Stopping recording promises
heal.addRecipe('ai', {
  priority: 1,
  prepare: {
    html: ({ I }) => I.grabHTMLFrom('body'),
  },
  steps: [
    'waitForVisible',
    'waitForInvisible',
    'waitForElement',
  ],
  fn: async args => {
    return ai.healFailedStep(args);
  },
});
Details
  • CodeceptJS version:3.6.6
  • NodeJS Version:18.17.0
  • Operating System:MacOS
  • Playwright: 1.46
Lingua principale
JavaScript
Stelle
4.2k
Fork
756
Merge medio
2g 9h
PR unite (30g)
16

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di codeceptjs/CodeceptJS

Tutte le issue di codeceptjs/CodeceptJS

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.