Internet Explorer Testing: Is It Still Necessary?

Updated 8 November 2026 · Standard formula, shown below

For most websites, testing in Internet Explorer is no longer necessary because Microsoft retired Internet Explorer 11 on many versions of Windows and ended support for it. It may still matter when a specific organization depends on an older system or has users who cannot yet move to a supported browser; in that case, treat IE testing as a documented compatibility exception, not a default requirement.

What happened to Internet Explorer?

Internet Explorer (IE) was Microsoft’s long-running web browser, but it was replaced by Microsoft Edge. Internet Explorer 11 was the final major desktop release. Microsoft ended support for the IE 11 desktop application on certain Windows 10 versions on June 15, 2022, and later disabled it on many of those systems, redirecting users to Edge. The precise transition depends on the Windows edition and servicing lifecycle: some environments, especially those tied to specialized or long-term-support releases, have different arrangements.

IE mode in Edge is not the same as keeping the standalone browser alive. It allows Edge to render selected sites using the Trident MSHTML engine associated with IE, while the rest of the browser remains Edge. Organizations can configure site lists so that legacy internal applications open in this mode. That capability is intended to support migration, not to make IE a suitable browser for general web use.

When is IE testing still necessary?

Testing is justified when there is concrete evidence that users or business processes still rely on IE-specific behavior. Examples include an internal application that only works in IE mode, an older intranet that uses ActiveX controls, or a managed workstation whose browser environment cannot yet be upgraded. A contractual support requirement can also make compatibility checks necessary, though the exact obligation depends on the agreement and supported platform.

Before adding IE to a test plan, establish who needs it and why. Ask IT or the application owner for usage data, a list of affected systems, and a migration plan. If no users, supported systems, or required workflows depend on IE, maintaining a permanent IE test suite usually wastes effort and can encourage continued reliance on an obsolete platform.

Keep testing temporarily if a named user group still runs a critical legacy workflow.
Test IE mode specifically if the supported setup is Edge configured to open a site in IE mode.
Stop testing when usage has ended, migration is complete, and stakeholders agree that IE is outside the support scope.

How to decide what to test

Start with the supported-browser policy and real user requirements, rather than assuming that every browser ever used needs coverage. Confirm the operating system and browser configuration too: a result from an old IE installation may not represent how the same application behaves in Edge’s IE mode. Record the target environment, the site list or compatibility settings, and the business task being checked.

Prioritize a small set of high-impact workflows: signing in, opening key records, submitting forms, printing or exporting documents, and completing any transaction the organization considers essential. Check layout and interaction as well as whether the page loads. If IE support is limited to one internal application, focus on that application instead of running the entire public website through an obsolete-browser matrix.

Use an isolated, organization-managed test environment where possible. Do not expose sensitive data or connect unsupported software to systems unnecessarily. If the only available test is an old physical or virtual machine, involve IT so that its network access, data, and lifecycle are handled under the organization’s normal controls.

Common compatibility problems

IE differs from modern browsers in its rendering engine and support for web standards and newer JavaScript features. A site that relies on modern CSS, JavaScript syntax, or browser APIs may fail to render or run correctly in IE. Legacy applications can have the opposite problem: they may depend on IE-only features such as ActiveX, older document modes, or behaviors that modern browsers intentionally do not reproduce.

Compatibility View and document modes can also affect how a page is rendered. A page may appear different depending on enterprise settings, intranet detection, or compatibility configuration. That is one reason a report saying “works in IE” is incomplete unless it identifies the exact machine and configuration.

Layout differences: older rendering behavior can affect spacing, fonts, and CSS features.
Script failures: JavaScript features used by current applications may not exist in IE.
Legacy dependencies: controls or plugins may work only in a narrowly configured older environment.
Configuration mismatch: IE mode, compatibility settings, and standalone IE are not interchangeable test targets.

For a modern public website, the better response to an IE failure is generally to define supported browsers clearly and make the site usable in current browsers, not to add increasingly complex workarounds for IE. For a business-critical legacy application, capture the failure and its business impact, then decide whether a contained short-term exception or a replacement project is appropriate.

Security, maintenance, and alternatives

An unsupported browser no longer receives the normal stream of browser security and compatibility updates. Continuing to rely on it can expose users to known risks and leave them with an experience that increasingly breaks as websites change. Testing itself does not make the browser safe, and passing a functional test does not demonstrate that an environment is secure.

Where legacy compatibility is unavoidable, use the supported Edge IE mode configuration on managed systems and follow Microsoft’s current documentation for the applicable Windows environment. Limit the exception to the sites that require it, restrict access where practical, and set an owner and review date. IE mode provides a transition path, but it does not eliminate the technical debt or remove the need to replace outdated applications.

For new development, test in currently supported browsers that match the audience and product policy. Browser automation tools and device labs can help cover those browsers, but an automated run in a modern browser does not prove IE compatibility. If a customer or employee specifically requires IE, verify that requirement and test the actual supported setup rather than relying on an emulator or an unrelated browser’s compatibility claim.

Frequently Asked Questions

Is Internet Explorer completely gone?
Not in every technical sense. The standalone IE 11 application was retired or disabled on many Windows systems, while certain specialized environments may differ. Edge’s IE mode can still render selected sites with the legacy engine.

Does Edge IE mode mean I should test all websites in IE?
No. Test IE mode only when a supported site or user workflow specifically depends on it. It is a compatibility option for selected legacy sites, not a general replacement for testing current browsers.

Can I use an IE emulator to prove my site works in Internet Explorer?
Not reliably. Emulators and compatibility tools may approximate particular behaviors, but they do not necessarily reproduce the target operating system, engine, or enterprise configuration. Validate in the actual supported environment if IE compatibility is a requirement.

Should a new website support Internet Explorer?
Usually not, unless the project has a verified audience or contractual requirement that explicitly includes it. State the supported browsers, test those browsers, and provide a suitable upgrade path for users on obsolete systems.

How do I know whether my organization still needs IE testing?
Ask IT and application owners for browser usage, affected workflows, and support requirements. Keep a narrowly scoped test only while a real dependency remains, and review it as part of the migration plan.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.