Theia: Consider using cypress for our UI tests
Suggested by @akosyakov :
https://www.cypress.io/ - looks like a better alternative to Selenium and writing browser based tests in general
marcdumais-work
All 5 comments
@epatpol maybe something to investigate quickly...
marcdumais-work
on 24 Jan 2018
Example of debugging: https://vimeo.com/242961930#t=264s
They also have a free dashboard for public projects: https://www.cypress.io/dashboard/
So one can investigate recorded snapshots for failed tests.
akosyakov
on 24 Jan 2018
Yes I just looked a bit into it, it sure does look interesting, but I haven't investigated further. I personally don't mind switching to that if it's easier to maintain ui tests.
epatpol
on 24 Jan 2018
I think we should rethink the whole ui test infrastructure. The ideal structure would be ui tests per packages. i.e packages/cpp and packages/workspace have their own ui tests which would launch a theia app with the bare minimum (just the current package and its dependency) and run the tests against this ui. I don't know how complicated/difficult that would be, but if someone considers switching to Cypress I think we should consider making that change also.
epatpol
on 13 Apr 2018
We've decided no to go with any integration testing framework, but own testing against Theia APIs.
akosyakov
on 8 Aug 2019
Related issues
Beetix
路
3Comments
akosyakov
路
3Comments
akosyakov
路
3Comments
vinokurig
路
3Comments
dhananjayharel
路
3Comments
Most helpful comment
I think we should rethink the whole ui test infrastructure. The ideal structure would be ui tests per packages. i.e packages/cpp and packages/workspace have their own ui tests which would launch a theia app with the bare minimum (just the current package and its dependency) and run the tests against this ui. I don't know how complicated/difficult that would be, but if someone considers switching to Cypress I think we should consider making that change also.