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.

no information about test error source/location

See original GitHub issue

i have to do many clicks to rig and test a feature, and when cypress fails to click, i get the following error:

  1) whatever:
     CypressError: cy.click() can only be called on a single element. Your subject contained 3 elements. Pass { multiple: true } if you want to serially click each element.
      at Object.cypressErr (https://shopware.vanilla/__cypress/runner/cypress_runner.js:68076:11)
      at Object.throwErr (https://shopware.vanilla/__cypress/runner/cypress_runner.js:68041:18)
      at Object.throwErrByPath (https://shopware.vanilla/__cypress/runner/cypress_runner.js:68068:17)
      at Context.click (https://shopware.vanilla/__cypress/runner/cypress_runner.js:54585:16)
      at Context.<anonymous> (https://shopware.vanilla/__cypress/runner/cypress_runner.js:63943:21)
      at https://shopware.vanilla/__cypress/runner/cypress_runner.js:63656:33
      at tryCatcher (https://shopware.vanilla/__cypress/runner/cypress_runner.js:7091:23)
      at Promise._settlePromiseFromHandler (https://shopware.vanilla/__cypress/runner/cypress_runner.js:5113:31)
      at Promise._settlePromise (https://shopware.vanilla/__cypress/runner/cypress_runner.js:5170:18)
      at Promise._settlePromiseCtx (https://shopware.vanilla/__cypress/runner/cypress_runner.js:5207:10)
      at Async._drainQueue (https://shopware.vanilla/__cypress/runner/cypress_runner.js:2028:12)
      at Async._drainQueues (https://shopware.vanilla/__cypress/runner/cypress_runner.js:2033:10)
      at Async.drainQueues (https://shopware.vanilla/__cypress/runner/cypress_runner.js:1907:14)
      at <anonymous>

how do i know which of the cy.click() cypress has a problem? at the moment i do it by trial-and-error, but that cant be the way… why not simply show the test file name and line number in the error?

$ ./node_modules/.bin/cypress --version
Cypress package version: 3.0.2
Cypress binary version: 3.0.2

Issue Analytics

State:
Created 5 years ago
Reactions:8
Comments:7 (3 by maintainers)

Top GitHub Comments

11reactions

elimydlarzcommented, Jun 25, 2019

I’d really like to see this feature. User journey tests (the kind of thing people will absolutely use Cypress for) are often long for a variety of reasons and not having a line reference for a failure is a huge problem.

6reactions

hlb-schmidtcommented, Jul 31, 2018

and why not simply show the error filename and line number?

Top Results From Across the Web

DISM Not finding source - Microsoft Q&A

I am having some difficulty with DISM, and it appears that nothing that I do will resolve the issue. I confirmed that the...

How to figure out in which file and code line a cypress test has ...

So in the below case the test throws with an error 'transt' is not defined. So I have added a debugger before the...

Troubleshooting Lookout for Metrics - AWS Documentation

The following topics provide troubleshooting information for errors and ... Error: No datapoint was found at the source location for time interval from ......

Diagnostic Infrastructure - MLIR - LLVM

Source location information is extremely important for any compiler, because it provides a baseline for debuggability and error-reporting.

Unable to fetch source Information for test method

Rebuild of solution works as expected and no error is reported. While we try to diagnose it, can you try rebuilding the solution,...