Feeling Lucky
Unit/System Tests
PR-5.3-dev
[#44683] - [5.3][cypress] test console command site:up & site:down
- Fixed in Code Base
- 9 Jan 2025
- Medium
- Build: 5.3-dev
- # 44683
- Diff
- alikon:cypress-4-cli-command
User tests: Successful: Unsuccessful:
Summary of Changes
add test for console command
- php cli/joomla site:up
- php cli/joomla site:down
Testing Instructions
npm cypress run --spec tests/System/integration/cli/SiteUpDown.cy.js
Actual result BEFORE applying this Pull Request
N/A
Expected result AFTER applying this Pull Request
conole command tested
Link to documentations
Please select:
-
Documentation link for docs.joomla.org:
-
No documentation changes for docs.joomla.org needed
-
Pull Request link for manual.joomla.org:
-
No documentation changes for manual.joomla.org needed
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | JavaScript Unit Tests |
| Labels |
Added:
Unit/System Tests
PR-5.3-dev
|
||
alikon
- comment
- 4 Jan 2025
Are Joomla System Tests not exclusively meant for testing the website frontend and backend?
i dont think so, in joomla we have something like 4 applications:
- frontend
- backend
- websrvices
- cli
so i consider a good pratice to test all of them with the same toolchian
| Title |
|
||||||
heelc29
- comment
- 8 Jan 2025
I have tested this item ✅ successfully on f6facfa
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/44683.
| Status | Pending | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2025-01-09 06:46:24 |
| Closed_By | ⇒ | laoneo |
laoneo
- comment
- 9 Jan 2025
Thanks!
From my perspective, testing the Joomla command-line tool client within Joomla System Tests is not ideal. This approach reintroduces a dependency that was intentionally removed by #44656 for valid reasons. Are Joomla System Tests not exclusively meant for testing the website frontend and backend? Could we consider having separate tests dedicated to the command-line tool instead?