Testing an Epic MyChart portal is not like testing a regular website. At a glance it may seem straightforward, but things get complicated fast. Custom features often load inside iframes. Scripts change the page after it loads. Every step must follow HIPAA rules. That is why test suites across the USA keep failing when they interact with an Epic portal, from San Diego to Los Angeles, San Francisco and San Jose.
At Bitcot, we see the issue come down to four factors. First, iframes: many apps built on SMART on FHIR sit inside frames, so tools that expect a single flat page cannot find the elements they need. Second, the page changes itself: custom scripts run after the page loads. They swap elements, regenerate IDs and reorder content, so a test that worked yesterday fails today even if the application is unchanged. Third, content arrives late: lab results, appointment slots and messages load after the page appears to be done. Fourth, compliance controls: every test must handle login, session timeouts and patient data safely under HIPAA rules.
What works?- Add test hooks at the source. This means using selectors that don’t change.
- Use Playwright to control the browser. It handles iframes and dynamic content better than other tools.
- Use Applitools for visual checks. It helps catch layout changes that code-based tests miss.
- Use AI agents to triage failures and repair tests, not to generate tests in bulk. Focus on fixing issues, not creating more.
Read the full guide by Bitcot: https://www.bitcot.com/epic-portal-test-automation-framework/
Comments
Post a Comment