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.

Sign up for GitHub

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

Jump to bottom

Unittest failure in Selenium/Customer/DynamicFields/DynamicFieldDatabase.t #1810

Closed
bschmalhofer opened this issue Jun 6, 2022 · 4 comments
Closed

Unittest failure in Selenium/Customer/DynamicFields/DynamicFieldDatabase.t #1810

bschmalhofer opened this issue Jun 6, 2022 · 4 comments
Labels
bug Something isn't working as intended
Milestone
OTOBO 10.1.6

Comments

@bschmalhofer
Copy link
Contributor

This is a new failure. Should be fixed for the next patch level release.
@bschmalhofer bschmalhofer added the bug Something isn't working as intended label Jun 6, 2022
@bschmalhofer bschmalhofer added this to the OTOBO 10.1.5 milestone Jun 6, 2022
@bschmalhofer
Copy link
Contributor Author

This might be a sporadic failure. I ran this as a single test script and it worked.

@stefanhaerter
Copy link
Contributor

Do you have further information about the failure?

@bschmalhofer
Copy link
Contributor Author

Here is the log output from two of my latest test runs. Not that the exception occurred at different locations.

issue_1810.log

@stefanhaerter
Copy link
Contributor

I've seen this problem earlier but couldn't reproduce it reliably. It occurs while testing the DynamicField of type Database within the following steps:

  • Searching an element via the standard input field and clicking it so that it is added as a result element
  • Searching an element via detailed search and clicking it in the resulting table so that it is added
  • Verifying that the added elements are actually present in the interface

Here the error occurs since the ResultElement2, which was added via detailed search, cannot be found. At first glance, I think this might be a timing issue or something related.

daxim added a commit that referenced this issue Jun 10, 2022
@daxim
Issue #1810: wait until element exists
1248443
daxim added a commit that referenced this issue Jun 17, 2022
@daxim
Issue #1810: wait until element exists
c70f2f0
@svenoe svenoe modified the milestones: OTOBO 10.1.5, OTOBO 10.1.6 Jun 20, 2022
svenoe added a commit that referenced this issue Jun 28, 2022
@svenoe
Merge pull request #1822 from RotherOSS/issue-#1810-sporadic-failure
7bdef7b 
Issue #1810: wait until element exists
@svenoe svenoe closed this as completed Dec 6, 2022
bschmalhofer added a commit that referenced this issue Apr 5, 2023
@bschmalhofer
Issue #1810: complete conversion to Test2::V0
19cbc36
bschmalhofer added a commit that referenced this issue Apr 5, 2023
@bschmalhofer
Issue #1810: reduce the scope of the variable $Success
de729a4
bschmalhofer added a commit that referenced this issue Apr 5, 2023
@bschmalhofer
Issue #1810: add a semicolon after call to wait_until.
21d30fa 
The semicolon is apparently not really needed, but it is used
in the sample code in the documentation of Selenium::Waiter.
Let's stick with the less confusion syntax.
bschmalhofer added a commit that referenced this issue Apr 5, 2023
@bschmalhofer
Merge pull request #2259 from RotherOSS/issue-#1810-tidying
4bcd23d 
Issue #1810 tidying
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working as intended
Projects
None yet
Milestone
OTOBO 10.1.6
Development

No branches or pull requests
3 participants
@bschmalhofer @stefanhaerter @svenoe