Refactor e2e tests to use page.setContent #4844
Labels
0 - new
New issues that need assignment.
Calcite (dev)
Issues logged by Calcite developers.
estimate - 5
A few days of work, definitely requires updates to tests.
needs milestone
Planning workflow - pending milestone assignment, has priority and/or estimate.
p - low
Issue is non core or affecting less that 10% of people using the library
testing
Issues related to automated or manual testing.
Test type
e2e
Which Component(s)
all
Unstable Tests
n/a
Test error, if applicable
No response
PR skipped, if applicable
Additional Info
Since
page.setContent
implicitly callspage.waitForChanges
we should use this everywhere in place of setting the html directly in thenewE2EPage()
constructor function. A codemod could be used to streamline updates.Further usage of
newE2EPage({ html })
should be prevented via linting rules.The text was updated successfully, but these errors were encountered: