Closed yasserfaraazkhan closed 3 years ago
Can you try a newer Cypress version (which is 7 now), version 3 is very very old and I don’t see this plug-in providing support for such an old test runner
Sent from my iPhone
On Jul 5, 2021, at 15:57, yasserfaraazkhan @.***> wrote:
Cypress: version: 3.7.0 Cypress grep: 2.5.1 Node: 12.18.0
my Test file:
describe('A', () => { it('B', { tags: @.' }, () => { console.log('in B'); }); it('C', { tags: @.', @.***'] }, () => { console.log('in C'); }); }); Error log:
1) An uncaught error was detected outside of a test: Uncaught TypeError: fn.call is not a function
This error originated from your test code, not from Cypress.
When Cypress detects uncaught errors originating from your test code it will automatically fail the current test.
Cypress could not associate this error to any specific test.
We dynamically generated a new test to display this failure. at context.describe.context.context (http://localhost:9090/__cypress/runner/cypress_runner.js:27045:10)
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.
@bahmutov In one of my projects it's working seamless with new version. But one of the main monolith project i'm working on, is in legacy angular and not likely to be upgrade any time soon.
I was hoping we can have a custom way of overriding it
block. ( I think this is doable).
My blocker in above approach is, how to let Cypress.run() to run or skip that particular it block
one more question:
Cypress-select-test
works, would it be recommend to keep using it as it has some JS support issues ?
Cypress: version: 3.7.0 Cypress grep: 2.5.1 Node: 12.18.0 Run command:
my Test file:
Error log: