You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
proposal/call for discussion: Testing joomla-cypress itself?
As a starting point, I could imagine to test calling each method at least once to avoid problems like #13. From my point of view, most of the problems with Cypress come with the HTML/CSS names and the specific way of the test implemention for Cypress. There are always different ways to implement something in Cypress. If we call every method one time for Joomla 4 and 5 I guess we catch 90% of the trouble. It could be extended later if detailed tests are needed to check the results.
Running with latest Joomla 4 and latest Joomla 5. To be discussed if we should support latest Joomla 3 or not. I would vote for supporting Joomla 3 too (as my plugin is supporting it), but i assume the maintenance effort is not reasonable as Joomla 3 is EOL?
I can imagine a docker-test environment with containers: mariadb, joomla4, joomla5 and cypress. Test can run headless. I can create such environment like in https://github.com/muhme/quote_joomla. I can imagine to run it with GUI too, e.g. to have a local Joomla 5.0.2 installation to test it.
What are you thinking? Does it fit in the environment of Joomla on the one hand and an NPM package on the other. Other ideas?
The text was updated successfully, but these errors were encountered:
muhme
changed the title
improvement: add tests for joomla-cpyress itself
improvement: add tests for joomla-cypress itself
Jan 20, 2024
proposal/call for discussion: Testing joomla-cypress itself?
As a starting point, I could imagine to test calling each method at least once to avoid problems like #13. From my point of view, most of the problems with Cypress come with the HTML/CSS names and the specific way of the test implemention for Cypress. There are always different ways to implement something in Cypress. If we call every method one time for Joomla 4 and 5 I guess we catch 90% of the trouble. It could be extended later if detailed tests are needed to check the results.
Running with latest Joomla 4 and latest Joomla 5. To be discussed if we should support latest Joomla 3 or not. I would vote for supporting Joomla 3 too (as my plugin is supporting it), but i assume the maintenance effort is not reasonable as Joomla 3 is EOL?
I can imagine a docker-test environment with containers: mariadb, joomla4, joomla5 and cypress. Test can run headless. I can create such environment like in https://github.com/muhme/quote_joomla. I can imagine to run it with GUI too, e.g. to have a local Joomla 5.0.2 installation to test it.
What are you thinking? Does it fit in the environment of Joomla on the one hand and an NPM package on the other. Other ideas?
The text was updated successfully, but these errors were encountered: