[MAGNOLIA-5045] Fix selenium integration tests Created: 20/May/13  Updated: 22/May/13  Resolved: 21/May/13

Status: Closed
Project: Magnolia
Component/s: integration tests
Affects Version/s: 4.5.9
Fix Version/s: 4.5.9

Type: Bug Priority: Neutral
Reporter: Roman Kovařík Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MAGNOLIA-5029 Components with areas does not behave... Closed
caused by MAGNOLIA-4892 Scroll bar not releasing focus after ... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   
  • MAGNOLIA-5029 forbid rendering of scripts, when a area is empty.
    PageEditorTest.testAddAreaOpensEditDialogOnOneAvailableComponent() relies on ID from the script. Also this test doesn't return from pop-up to parent window which causes random failure of following tests.
  • MAGNOLIA-4892 changed the main event from mouseUp to clickEvent.
    PageEditorTest.testCookieValueMatchesSelectedComponent() has to respect this}.
  • PageEditorTest.testEditBarOfSelectedComponentIsVisibleAfterPageReload().
    selenium.click("link=...") redirects to link target even if the link is disabled.


 Comments   
Comment by Jan Haderka [ 20/May/13 ]

It's ok to move this issue to the next release if you don't finish with it before the rest are done.

Generated at Mon Feb 12 04:01:27 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.