Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Cannot execute browser manipulations step step by step #2150

Closed
helen-dikareva opened this issue Feb 20, 2018 · 1 comment
Closed

Cannot execute browser manipulations step step by step #2150

helen-dikareva opened this issue Feb 20, 2018 · 1 comment
Assignees
@AndreyBelym
Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot. TYPE: bug The described behavior is considered as wrong (bug).
Milestone
Sprint #10

Comments

@helen-dikareva
Copy link
Collaborator

Press Next Step button. Debugging doesn't stop before takeScreenshot/takeElementScreenshot action.

fixture `f`
    .page `https://www.amazon.com/`;

test('debugging s-b-s', async t => {
    await t
        .resizeWindow(500, 500)
        .debug()
        .takeScreenshot()
        .takeScreenshot()
        .takeScreenshot()
});
@helen-dikareva helen-dikareva added the TYPE: bug The described behavior is considered as wrong (bug). label Feb 20, 2018
@AlexanderMoskovkin AlexanderMoskovkin added this to the Sprint #10 milestone Feb 20, 2018
AndreyBelym added a commit to AndreyBelym/testcafe that referenced this issue Feb 21, 2018
@AndreyBelym
Fix step-by-step execution of window manipulations (closes DevExpress…
7320c18 
…#2150)
@AndreyBelym AndreyBelym changed the title Cannot execute step step by step Cannot execute browser manipulations step step by step Mar 1, 2018
@lock
Copy link

lock bot commented Mar 28, 2019

This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.

@lock lock bot added the STATE: Auto-locked An issue has been automatically locked by the Lock bot. label Mar 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 28, 2019
kirovboris pushed a commit to kirovboris/testcafe-phoenix that referenced this issue Dec 18, 2019
@AndreyBelym @kirovboris
Fix browser manipulation issues (closes DevExpress#2150, closes DevEx…
852e5fc 
…press#2146) (DevExpress#2158)

* Fix step-by-step execution of window manipulations (closes DevExpress#2150)

* Remove screenshot when can't extract element from it (closes DevExpress#2146)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@AndreyBelym AndreyBelym

Labels
STATE: Auto-locked An issue has been automatically locked by the Lock bot. TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Milestone
Sprint #10
Development

No branches or pull requests
3 participants
@AndreyBelym @helen-dikareva @AlexanderMoskovkin