onthespotqa / cypress-macros Goto Github PK

Cypress will error if I use {@bogus} variable name, and macros will error if I use a {$bogus} macro variable. Nobody cares if I ask for {@real.bogus} or {$real.bogus}; they evaluate to undefined.

Guard our use of lodash/get and raise an error if we get something that's undefined; the implication is that if we're using it in a macro, it should have some value.

We need a way to register new $foo variables. Some decisions to make:

1. memoize or not?
2. reset on every test case? (seems like yes!)
3. how to register: normal beforeEach or special registry?

It's got issues with Cypress 4.x and needs to go away. (evalMacros does just as good a job these days anyway.)

So we can be all official and have the siny ci badge.

a) Module-scope vars can be double initialized (etc) if modules are required multiple times (e.g. during tests).

b) No support for variables that are a simple scalar.

c) Improper use of chai be causes false green tests.

d) Tests mix sync/async code with no synchronization; will always be red.