End-users need to understand, that TestComplete typically supports Chrome and Edge versions that are 2–3 versions behind the latest release due to the following reasons:
- Browser internals change frequently - each browser update can introduce changes to the DOM, JavaScript engine, and debugging APIs, which may break existing functionality.
- Stability and compatibility testing - SmartBear needs time to test and validate each new version to ensure stable integration and prevent test failures.
- Enterprise alignment - many enterprise environments lock browser versions for consistency, so supporting slightly older versions aligns with real-world usage.
- Reliability over recency - prioritising stability helps avoid flaky tests and ensures a predictable testing environment.
- Changing APIs (CDP) - Chrome and Edge use the Chromium DevTools Protocol, which evolves frequently. TestComplete must adapt its internal mechanisms accordingly before offering support.
In short, this delay is intentional to ensure reliability and consistency across different environments.
Many organisations use locked or controlled browser versions in their environments to ensure consistency and compliance. TestComplete’s support for slightly older browser versions aligns with these enterprise practices, ensuring stable, predictable testing across teams. However, it seems like many organisations do not implement to this rule!