Dynamics 365 and Infor M3 Experience with Playwright?

Hi, just out of curiosity, is this for test automation on custom extensions/plugins/apps (whatever they're called) for Dynamics/Infor M3?

I think as long as it's web based (using HTML, CSS, JavaScript, HTTP(s), etc.) then it should work.

How maintainable and reliable it will be depends on how test-automation-friendly their pages and the custom 'extensions' are, like having good semantic markup and good usability attributes.

Hi, I have started using Playwright to automate regression E2E tests for dynamics 365 - have create close to 100 so far with some very long complex e2e scenario's. Main challenge is determining the locators. Biggest tip is to use retry-trying assertions and apply AAA (Arrange, Act & assert).

What is AAA?

https://automationpanda.com/2020/07/07/arrange-act-assert-a-pattern-for-writing-good-tests/ Arrange, Act, Assert

Just for clarification for everyone, by retry-trying assertions, you mean auto retry ones and expect.poll(...) and expect.toPass(...)

https://playwright.dev/docs/test-assertions#expectpoll

I apply AAA this way:

async openEmploymentHistory() { // Arrange, make sure we are in a position to continue await expect(this.button.WorkTab).toBeVisible();

// Act - Do what we want to do.
await this.button.WorkTab.click();
await this.link.EmploymentHistory.click();

// Assert - Confirm act has done what we wanted.
await expect(this.combo.startDate).toBeVisible({timeout: 10 * 1000});

}

See this for re-trying assertions. Fantastic part of Playwright! https://playwright.dev/docs/test-assertions

Dynamics can be a bit slow in doing it's actions and Playwright can get a bit ahead of it. So, I have found the re-trying assertions are a must 🙂