Jonas Amundsen
Jonas Amundsen
Hi, Evan Thanks for a wonderful library! I have a question / something regarding the `sources` property of outputted (inline) sourcemaps. Given I have two files, ```mjs // foo.mjs export...
Hey, Due to the removing of screenshots after reading their content [1], Cypress isn't able to name consecutive screenshots in accordance to the docs [2]. This is quite unpractical if...
Hi, Retry-ability is a core feature of Cypress and part of what makes it so usable. Cypress also provides APIs to create custom commands that adhere to this pattern (using...
This utility, along with the actual XPathEvaluator.evaluate, can return primitive values. For the utility's case, these are *not* wrapped in jQuery, but it appears as if that is not taken...
### What would you like? Similar to https://github.com/cypress-io/cypress/issues/2283, I'd like to propose implementing `test:after:run` as a plugin event, mirroring the driver event, specifically in the sense that it's invoked for...
# Transfer of ownership Due to personal reasons, the previous maintainers of this package are stepping down and handing the reigns over to me, a long-time contributor to the project...
SSIA basically. Static code analyses with fallback to evaluation to cover more use-cases (EG. where evaluation fails un-mocked expression at top-level, ref. https://github.com/badeball/cypress-cucumber-preprocessor/issues/1120).
Per today, source maps aren't / can't be utilized. EG. when multiple step definitions match, we throw an error ``` Error: Multiple matching step definitions for: a step a step...
Example of this: ```js Given(/^foo {string}/, () => {}); ``` This is unequivocally an error and we can give a more appropriate message than that "a step definition is missing"....