Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix System test com_privacy consent (#42523) #43400

Merged
merged 1 commit into from
Apr 30, 2024
Merged

Conversation

muhme
Copy link
Contributor

@muhme muhme commented Apr 29, 2024

After discussion with Alikon the fix is simple 10 milliseconds waiting time after changing sorting order. The five failures were reproducable in 4.4-dev and fixed and it is expected it works the same way for 5.1.

Pull Request for Issue #42523.

Summary of Changes

After selecting a new sorting order it is needed to wait for the POST request to be fullfilled.
This is simple possible by waiting 10 milliseconds. 1 millisecond was enough, but to be save,
10 milliseconds are used.

Testing Instructions

In system test environment with Cypress test e.g. headless:
npm run cypress:run -- --spec tests/System/integration/administrator/components/com_privacy/Consent.cy.js
Please consider this is a racing condition. On drone the test were ?always? successful.
Therefore test first the failure, then patch and test success.

Actual result BEFORE applying this Pull Request

5 of the 24 tests in the spec failed.

Expected result AFTER applying this Pull Request

All 24 tests in the spec are successful.

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

After discussion with Alikon the fix is simple 10 milliseconds waiting time
after changing sorting order. The five failures were reproducable in 4.4-dev
and ifixed and it is expected it works for 5.1 the same way.
@brianteeman
Copy link
Contributor

I have tested this item ✅ successfully on f26ce42

Conmfirmed bug (again)

Applied PR

Bug gone - Thank YOU!!


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/43400.

@alikon
Copy link
Contributor

alikon commented Apr 29, 2024

I have tested this item ✅ successfully on f26ce42


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/43400.

@alikon
Copy link
Contributor

alikon commented Apr 29, 2024

RTC


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/43400.

@joomla-cms-bot joomla-cms-bot added the RTC This Pull Request is Ready To Commit label Apr 29, 2024
@Quy Quy added the PR-4.4-dev label Apr 29, 2024
@laoneo laoneo added this to the Joomla! 4.4.5 milestone Apr 30, 2024
@laoneo laoneo merged commit 301bdf2 into joomla:4.4-dev Apr 30, 2024
4 checks passed
@laoneo
Copy link
Member

laoneo commented Apr 30, 2024

Thanks!

@joomla-cms-bot joomla-cms-bot removed the RTC This Pull Request is Ready To Commit label Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants