silbinarywolf / cypress-aurelia-unit-test Goto Github PK

The problem
Some code is falling over in Cypress only because bind() and attached() are being called twice. Should remove the offending code.

The problem
Cypress has an issue where tests will run perfectly fine when using cypress open but fails when using cypress run.

Related to:

• cypress-io/cypress#3082

The problem
After completing/merging a fix for #9, any components I had that were @containerless no longer rendered correctly.

I know that removing the manual attached()/bind() was the correct thing so I need to investigate other solutions.

For example, maybe instead of doing "compile" on the view beforehand, I can just do "enhance" and be done with it.

cypress-io/cypress#4069

The problem
Previous changes related to only using enhance mean that I've lost the reference to the viewModel.

The solution
Walk the nodes that have been created and find the viewModel via the controller on the HTMLElement. (access the au property)

Relies on #1

Why
Consider allowing bindingContext to be a function as well.
A potential benefit is that you can use "Container.instance.get" after aurelia has called start.

const bindingContext = this.bindingContext;
//const bindingContext = typeof(this.bindingContext) === 'function' ? this.bindingContext() : this.bindingContext;

Why?
aurelia-dialog crashes Cypress when you try to use it with unit testin, so I have some code that removes it for you and tells you it was removed for that reason.

The use-case is so that you can import your "main" configuration file from your app without adjusting it.