-
Notifications
You must be signed in to change notification settings - Fork 74
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 UnitTest Failures #3100
Comments
Removed errantly added FieldNames param from FormUpdate.
Removed errantly added FieldNames param from FormUpdate.
Things look better now. Here is the result of the latest run, with "local in Eventhandler commented out":
|
Thank you very much =) |
The latest test run with EventHandler.pm as checked in:
|
This looks very similar to the failures I got when running the CKEditor 5 branch. Since this branch is merged, the failures seem to be related to CKEditor 5 changes. |
Here is the latest run. I think that the failures are not surprising, but the run time is. It was over 3h.
My suspicion is that strange things happen in global desctruction.
|
I would consider a runtime of about 1.5 to 2 hours normal, based on my experience upon now - 3 hours is a bit of an outlier, indeed. |
…or value shortening done by BuildSelection().
EditFieldRender should be fixed with merging #3466. Had a quick discussion with Sven about AgentTicketActionCommonDraft. I will precisely check this and if there is no further meaning in checking for a dialog, I will just remove the check as the label turning red and the error tooltip popping up is the correct behavior if no server error occured. |
Added focus handling. Removed duplicated 'Set back' test.
We do not expect an error dialog due to js validation failing before.
Taking the changes of #3487 and #3489 into account, failures should be down to only one, which is AgentTicketOwner. I'm yet unsure what this failure indicates, as I found that clicking on the selection filter checkbox in the UI applies the filter and triggering a click event via js / Selenium does not, but I have not yet found the reason behind this. So it is possible that this indicates a real bug. |
Added focus handling. Removed duplicated 'Set back' test.
We do not expect an error dialog due to js validation failing before.
The latest run looks pretty good. The failure in AgentTicketZoom.t could be related to the recent change 61ef164 .
|
Run just before the release of OTOBO 11.0.3. The failure in _ConfiguredRepositoryDefinitionGet.t _ is already fixed.
|
First run on rel-11_1 looks good, with the expected two failing test scripts:
|
and add some more code comments. But the test failure persists.
and add some more code comments. But the test failure persists.
I tried to understand the test failure in scripts/test/Selenium/Agent/AgentTicketActionCommon/AgentTicketOwner.t . But to no avail. The event that should filter the user list seems to be registered in otobo/var/httpd/htdocs/js/Core.UI.InputFields.js Line 2334 in ce4a136
The selection seems to work fine when executed manually in a browser. |
I guess that this is due to some event being executed on key(down|press|up), but couldn't manage to find out which one and where. |
In the code I have seen registrations for |
To me, it looks a lot like the failures in AgentTicketZoom and AgentTicketOwner are due to the same issue. Should we shift this into a separate issue? |
@stefanhaerter Yes, please do so. |
Closing this issue as there now is a dedicated issue #3563 for the remaining two failures. |
The text was updated successfully, but these errors were encountered: