[
https://issues.apache.org/jira/browse/IGNITE-7805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Borisov updated IGNITE-7805:
---------------------------------
Description:
*What happens:*
The "Testing setting notifications" test fails when run under macOS. During the
issue initial research I managed to find that AngularStrap modal animations
take way more time to complete compared to a regular, non-TestCafe environment.
The broken animation makes elements appear in an unexpected order, which in
turn causes TestCafe selectors to select wrong elements or correct elements,
but at wrong time. The cause might lie in both TestCafe and our app code.
*What to do:*
Find out the cause of the issue. If it lies in TestCafe, find a corresponding
GitHub issue or report one (don't forget about a minimal reproduction scenario
the TestCafe guys can use). If there's something wrong with either our own E2E
or web console code, try to fix it.
was:The "Testing setting notifications" test fails when run under macOS.
During the issue initial research I managed to find that AngularStrap modal
animations take way more time to complete compared to a regular, non-TestCafe
environment. The broken animation makes elements appear in an unexpected order,
which in turn causes TestCafe selectors to select wrong elements or correct
elements, but at wrong time. The cause might lie in both TestCafe and our app
code.
> Web console: fix admin-panel E2E test under macOS
> -------------------------------------------------
>
> Key: IGNITE-7805
> URL: https://issues.apache.org/jira/browse/IGNITE-7805
> Project: Ignite
> Issue Type: Bug
> Reporter: Ilya Borisov
> Assignee: Ilya Borisov
> Priority: Minor
>
> *What happens:*
> The "Testing setting notifications" test fails when run under macOS. During
> the issue initial research I managed to find that AngularStrap modal
> animations take way more time to complete compared to a regular, non-TestCafe
> environment. The broken animation makes elements appear in an unexpected
> order, which in turn causes TestCafe selectors to select wrong elements or
> correct elements, but at wrong time. The cause might lie in both TestCafe and
> our app code.
> *What to do:*
> Find out the cause of the issue. If it lies in TestCafe, find a corresponding
> GitHub issue or report one (don't forget about a minimal reproduction
> scenario the TestCafe guys can use). If there's something wrong with either
> our own E2E or web console code, try to fix it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
