[MGNLCE-124] Parallelise Selenium UI test execution Created: 16/Nov/17  Updated: 23/Feb/18  Resolved: 09/Feb/18

Status: Closed
Project: Community Edition
Component/s: None
Affects Version/s: None
Fix Version/s: 5.5.10, 5.6.2

Type: Task Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relation
is related to MGNLCE-130 Let the whole CE be executed as a sin... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: Improve QA setup
Sprint: Basel 123, Basel 124, Basel 125, Basel 126, Basel 127, Basel 129, Basel 130, Basel 131, Basel 132, Basel 133, Basel 134
Story Points: 34
Business Value: 34

 Description   

Main idea is to run at least some of the Mgnl UI test cases in parallel fashion (note that suites can still run one by one, but the test cases might be executed concurrently). For simplicity we can start with the suites that don't require a lot of preliminary work to be done (i.e. the test cases are independent from each other already and can be executed at the same time).

Related technologies:

  • Selenium grid (to support multiple connections)
  • JUnit extensions: since we're still living in JUnit 4 realm that'd be the Rules and Runners (schedulers), see https://github.com/junit-team/junit4/wiki/Custom-runners for more inspriration.
  • Magnolia test framework would need additional tools (e.g. direct access to workspaces or a network utility/servlet).

Generated at Mon Feb 12 00:06:30 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.