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.

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

Click on debugging panel has an affect on the tested page #1200

Closed
AlexanderMoskovkin opened this issue Feb 1, 2017 · 2 comments
Closed
Assignees
Labels
AREA: client STATE: Auto-locked An issue has been automatically locked by the Lock bot. SYSTEM: UI TYPE: bug The described behavior is considered as wrong (bug).
Milestone

Comments

@AlexanderMoskovkin
Copy link
Contributor

AlexanderMoskovkin commented Feb 1, 2017

it's related to the new t.debug() action (#918)

When the tests is stopped on debug() and some element is focused on the page, click on the resume test button leads to active element changing but it should not.

Test for check it:

test('Dealing with text using keyboard', async t => {
    await t
        .typeText(page.nameInput, 'Peter Parker')           // Type name
        .click(page.nameInput, { caretPos: 5 })             // Move caret position
        .debug()
        .pressKey('backspace')                              // Erase a character
        .expect(page.nameInput.value).eql('Pete Parker');
});
@AlexanderMoskovkin AlexanderMoskovkin added AREA: client SYSTEM: UI TYPE: bug The described behavior is considered as wrong (bug). labels Feb 1, 2017
@AlexanderMoskovkin AlexanderMoskovkin added this to the Sprint #4 milestone Feb 1, 2017
@helen-dikareva
Copy link
Collaborator

#1290 fixed it

@lock
Copy link

lock bot commented Mar 29, 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 29, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
AREA: client STATE: Auto-locked An issue has been automatically locked by the Lock bot. SYSTEM: UI TYPE: bug The described behavior is considered as wrong (bug).
Projects
None yet
Development

No branches or pull requests

2 participants