You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running Playwright locally and using playwright-qase-reporter to link to Qase. However, when I set the following configuration in Qase, every published test case is being updated to isManual=true. It'd be chill if this didn't happen or if there was a config to toggle.
import{ProspectSteps}from'@Playwright/common/steps/prospects.steps';import{qase}from'playwright-qase-reporter';import{expect,test}from'playwright/test';test(qase(14,'Cannot edit the property billing contact'),async({ page })=>{qase.fields({priority: 'high',});constprospectSteps=newProspectSteps(page);awaitprospectSteps.openProspectsPage();awaitprospectSteps.openEditProspectModal();expect(awaitpage.getByLabel('Existing contact*').isDisabled()).toBeTruthy();});
Attached are the project configurations.
I'm unable to set Update test cases from automated results without this happening which is rather frustrating. I'm just going to disable updates for now which is fine, but I wanted to bring some awareness.
The text was updated successfully, but these errors were encountered:
robertgagnon726
changed the title
playwright-qase-reporter updates automated test cases to isManual=true
[Bug][Playwright] updates automated test cases to isManual=true
Feb 2, 2025
I'm running Playwright locally and using playwright-qase-reporter to link to Qase. However, when I set the following configuration in Qase, every published test case is being updated to isManual=true. It'd be chill if this didn't happen or if there was a config to toggle.
Versions:
Related Playwright config
Test Case
Attached are the project configurations.
I'm unable to set
Update test cases from automated results
without this happening which is rather frustrating. I'm just going to disable updates for now which is fine, but I wanted to bring some awareness.The text was updated successfully, but these errors were encountered: