question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cypress Doesn't Finish Typing Strings Before Continuing to Next Field

See original GitHub issue

Current behavior:

When typing a long string into an input field, such as an email address to login in our case, Cypress 3.5.0 appears to no longer type the entire string. It bails on typing the complete string after the period in the email and never completely types the string. For example, test@webdomainhere.com would be typed as test@webdomainhere. in our app, failing the login.

I have also seen similar things with usernames using mixed case, such as associateEnabled would be typed as associate, stopping before the capital letter in the string.

Due to this bug we have had to roll back to using Cypress 3.4.1, where this worked fine.

Example screenshot showing a failed login in Cypress 3.5.0 where the email should’ve had ‘com’ typed after the period:

Screen Shot 2019-10-25 at 3 00 45 PM

Desired behavior:

Entire string passed to a cy.type() function should be typed into the input field.

Steps to reproduce: (app code and test code)

Type a long string, such as a long email address into a form field and then move on to a password field with a .click() and see that the end of the first string isn’t entered.

Versions

Cypress v3.5.0 (v3.4.1 works fine, we have had to roll back) Mac OSX 10.14.6 Electron 61 / Chrome 78

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:28
  • Comments:109 (25 by maintainers)

github_iconTop GitHub Comments

32reactions
jennifer-shehanecommented, Oct 28, 2019

Unfortunately we have to close this issue as there is not enough information to reproduce the problem. This does not mean that your issue is not happening - it just means that we do not have a path to move forward.

Please comment in this issue with a reproducible example and we will reopen the issue. 🙏

15reactions
TheWanderingWalnutcommented, Oct 28, 2019

@jennifer-shehane , I am unsure what you’re looking for. Simply use cy.type() on an input field with a string with mixed case and it will reproduce the problem. This happens on various login screens around our app which I cannot share as they are proprietary. Please let me know what you’re expecting for this bug to be investigated

Read more comments on GitHub >

github_iconTop Results From Across the Web

Solve Flake In Cypress Typing Into An Input Element
The cy.type command simply waits for the input element to be enabled (it is a built-in actionability check) before typing. You can see...
Read more >
How to resolve missing characters bug in Cypress type ...
So the solution was to add a space at the end of the string: this.getSelect2Input().invoke('val', str).trigger('change').type(' ');. It works ...
Read more >
type - Cypress Documentation
Cypress will fire input only if typing that key modifies or changes the value of the element.
Read more >
Avoid Flake When Typing Into The Input Elements ... - YouTube
The fast test runner does not know about the re-renders and keeps "losing" part of the input string when typing into the visible...
Read more >
How to type and press ENTER with Cypress
This way, Cypress will type the text and simulate the ENTER key is pressed. There is nothing new in the other test (...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found