Cypress testing

[jptissot]

Having fun with some e2e testing using Cypress

[jptissot]

@sebastienros What do you think about writing a npm package for the generic functions and publishing it as a seperate npm package ? This would allow people that write sites with OC to easily write e2e tests for their sites by reusing some of our functions to interact with the admin UI ?

[sebastienros]

No new npm package to maintain. Not soon at least. One more thing to maintain, publish, take PRs on ...

[jptissot]

I think I will revive this PR. Maybe split the work of adding id's, classes or data attributes to elements of the admin UI in smaller Pr's to keep this one targeted.

[jptissot]

I am writing a set of commands / utilities for Cypress in a separate package that can be shared between projects.
See https://github.com/jptissot/cypress-orchardcore

[jptissot]

This is ready for review. Need to investigate why the site(s) do not run in https.

Once this is merged, I will make other smaller pr's that improve the selectors of the admin interface along with implementing supporting commands in https://github.com/jptissot/cypress-orchardcore

[Skrypt]

I will need to try it to review it. Might take some time.

[hishamco]

@jptissot just a very late question why you choose Cypress over normal ASP.NET Core testing? Is it access the HTML elements or is there something further I don't aware of

Thanks

[Skrypt]

We have unit tests, integration tests coming from ASP.NET Core testing. But we use https://github.com/puppeteer/puppeteer to run functional (e2e) tests. I think Cypress is just pushing those functional test one step further.

[hishamco]

Thanks Jasmin, is it something like Selenium?

[jptissot]

Todo

• Docs on how to setup cypress in your project
• Visual studio solution

[Skrypt]

On the OrchardCore.sln file there's a solution folder in which we should remove the old linked files and instead add the Cypress tests. /test/Functional/*