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
Few months ago I asked if there's a way to save a screenshotAfterFail of a session + the original browser with Webdriver post .
A pr was created but looks like it doesn't work 100% of the time, I can't get all the screenshots like in the PR description.
I made a version of the test created on the PR to test it out.
Scenario('should save screenshot for sessions @session', async ({ I }) => {
await I.amOnPage('/');
await I.saveScreenshot('original.png');
await I.amOnPage('/browsevideos');
await I.saveScreenshot('main_session.png');
session('john', async () => {
await I.amOnPage('/browsevideos');
await I.see('Fake text'); // Fails here
});
});
What do you get instead?
I get all the screenshots except the after fail screenshot of the main browser.
but appears as artificat on the output
Output with ---verbose
› john - Screenshot is saving to ./output/[email protected]
› Screenshot of john session has been saved to ./output/[email protected]
› <Error: ENOENT: no such file or directory, open './output/[email protected]'>
Details
CodeceptJS version: 3.6.7
The text was updated successfully, but these errors were encountered:
It helps a lot to have the screenshots for debug, when you have scenarios with more than 2 sessions.
does anyone have the same problem? maybe it's only on my side..
What are you trying to achieve?
Few months ago I asked if there's a way to save a screenshotAfterFail of a session + the original browser with Webdriver post .
A pr was created but looks like it doesn't work 100% of the time, I can't get all the screenshots like in the PR description.
I made a version of the test created on the PR to test it out.
What do you get instead?
I get all the screenshots except the after fail screenshot of the main browser.
but appears as artificat on the output
Output with ---verbose
Details
The text was updated successfully, but these errors were encountered: