[#48341] - [5.4] system tests for filter field of content category view
- Fixed in Code Base
- 5 Sep 2026
- Medium
- Build: 5.4-dev
- # 48341
- Diff
- heelc29:5.4/system-tests/issue-46354
User tests: Successful: Unsuccessful:
Pull Request resolves # .
- I read the Generative AI policy and my contribution is either not created with the help of AI or is compatible with the policy and GNU/GPL 2 or later.
Summary of Changes
- adds system test to covers issues #46354, #46520 #48313 and the fix #48339
- covers also broken filter function in #47774 and the fix for it #48234
Testing Instructions
ci/cd (cypress)
run specs site/components/com_content/Category.cy.js
Actual result BEFORE applying this Pull Request
not tested
Expected result AFTER applying this Pull Request
tested
Link to documentations
Please select:
- No documentation changes for guide.joomla.org needed
- 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.4-dev
|
||
NOTE: to get test pass, an update of joomla/registry is necessary, as the new tests triggers a new PHP 8.5 deprecation joomla-framework/registry#89
@heelc29 The mentioned framework PR has been merged, and a new release has been made: https://github.com/joomla-framework/registry/releases/tag/3.0.3
Do you want to do the update of joomla/registry here in this PR? Or shall we do that with a separate PR?
It is just running a composer install and then a composer update joomla/registry and then commit the changed composer.lock. No change needed for composer.json and so no hash change for the lock.
I have that change already prepared and could apply it to your branch for this PR here if you want.
NOTE: to get test pass, an update of joomla/registry is necessary, as the new tests triggers a new PHP 8.5 deprecation joomla-framework/registry#89
@heelc29 The mentioned framework PR has been merged, and a new release has been made: https://github.com/joomla-framework/registry/releases/tag/3.0.3
Do you want to do the update of joomla/registry here in this PR? Or shall we do that with a separate PR?
It is just running a composer install and then a composer update joomla/registry and then commit the changed composer.lock. No change needed for composer.json and so no hash change for the lock.
I have that change already prepared and could apply it to your branch for this PR here if you want.
Update: I have meanwhile created PR #48372 .
I have tested this item ✅ successfully on ce466fc
I've successfully verified in the log of the CI action here https://github.com/joomla/joomla-cms/actions/runs/33889271716/job/101077347620?pr=48341#step:7:1917 that the new tests have run and have succeeded.
Before PR #48372 was merged into 5.4-dev and this PR was updated to that change, the tests have failed as expected, see log here: https://github.com/joomla/joomla-cms/actions/runs/33324241525/job/99291751966#step:7:1917
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48341.
I have tested this item ✅ successfully on ce466fc
I've successfully verified in the log of the CI action here https://github.com/joomla/joomla-cms/actions/runs/33889271716/job/101077347620?pr=48341#step:7:1917 that the new tests have run and have succeeded.
Before PR #48372 was merged into 5.4-dev and this PR was updated to that change, the tests have failed as expected, see log here: https://github.com/joomla/joomla-cms/actions/runs/33324241525/job/99291751966#step:7:1917
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48341.
I have tested this item ✅ successfully on c35f73d
Tested with JBT
- Before PR tested with 5.4.5 installation
- Running
scripts/test 54 system site/components/com_content/Category.cy.js- Seen 5 tests passing
- Copied over the three modified System Test files from this PR
- Seen 9 tests running, two of them failing and one skipped
- Running
- Installed current 5.4-dev branch and applied PR with Patch Tester
- Category System Test is running with 9 tests passed
- Running second time the Category System Test with all 9 tests passed
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48341.
I have tested this item ✅ successfully on c35f73d
Tested with JBT
- Before PR tested with 5.4.5 installation
- Running
scripts/test 54 system site/components/com_content/Category.cy.js- Seen 5 tests passing
- Copied over the three modified System Test files from this PR
- Seen 9 tests running, two of them failing and one skipped
- Running
- Installed current 5.4-dev branch and applied PR with Patch Tester
- Category System Test is running with 9 tests passed
- Running second time the Category System Test with all 9 tests passed
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48341.
| Status | Pending | ⇒ | Ready to Commit |
RTC
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48341.
RTC
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/48341.
| Status | Ready to Commit | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2026-09-05 15:10:19 |
| Closed_By | ⇒ | muhme | |
| Labels |
Added:
RTC
|
||
Thank you very much @heelc29 for your contribution. Thank you @laoneo for review. Thank you @richard67 for testing.
@heelc29 The mentioned framework PR has been merged, and a new release has been made: https://github.com/joomla-framework/registry/releases/tag/3.0.3
Do you want to do the update of joomla/registry here in this PR? Or shall we do that with a separate PR?
It is just running a
composer installand then acomposer update joomla/registryand then commit the changedcomposer.lock. No change needed forcomposer.jsonand so no hash change for the lock.