-
Type:
Story
-
Status: Closed (View Workflow)
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:
-
Sprint:2021.R4 New Features Sprint 2, 2021.R5 New Features Sprint 1, 2021.R5 New Features Sprint 2
-
SCRUM Team:Brotherhood of Mutants
-
Story Points:5
-
Work Type Classification:Sustaining
Story
As a developer, I would like to update the existing automation framework to support M2 pages, so that I can write M2 automated tests
Acceptance Criteria
- Research and develop a common method to identify through configuration that the page is using M2 and not MxConnect
- Come up with a sample test, navigating to an M2 page
- Confirm the routing works through the menu to an M2 or MxConnect page
Note: M2 pages will eventually replace MxConnect pages
- implements
-
CFAMX-12484 InFORM Angular Technology Update
-
- In Development
-
1.
|
Review Test Scripts |
|
Done | Unassigned |
|
||||||||
2.
|
Deploy |
|
Done | Unassigned |
|
||||||||
3.
|
Functional Review with QA |
|
Done | Unassigned |
|
||||||||
4.
|
DIT |
|
Done | Unassigned |
|
||||||||
5.
|
Split M2 and MxConnect testng.xml files. |
|
Done | Caner Saritac |
|
||||||||
6.
|
Create Some sample M2 tests |
|
Done | Caner Saritac |
|
||||||||
7.
|
Implement Conditional JsWaiter |
|
Done | Caner Saritac |
|
||||||||
8.
|
Fix Build/Deploy Process to pickup new test.ng files |
|
Done | Caner Saritac |
|
