For Testers‎ > ‎Backend Testing‎ > ‎

Multi-process Architecture (test plan)

Overview

Google Chrome's multi-process architecture means that there are many processes communicating with each other. Unlike current browsers, Google Chrome is built like an operating system to run web sites in a safe and robust way, using multiple OS processes to isolate web sites from each other and from the browser itself. This improves robustness because each process runs in its own address space, is scheduled by the operating system, and can fail independently. Google Chrome supports four different architectures (process-per-site, process-per-site-instance, process-per-tab, single-process) that affect how the browser is split into OS processes. By default, Chrome uses OS processes to isolate different web sites from each other.

Testing strategy

The Primary Focus will be on verifying whether the multi-process architecture is working as per the design on different operating systems (Microsoft Windows XP and Vista).

What needs to be tested

Basic testing

Testing environment

  • Operating systems: Windows Vista SP1, Windows XP SP2 and SP3
  • Above configurations with antivirus/antispyware: Norton 2008, McAfee, Symantec, Sophos AV, TrendMicro, PC Tools Spyware Doctor, Lavasoft Ad-ware, Webroot Spy Sweeper, Zone Alarm Internet Security Suite, Windows Live one Care, Kaspersky Internet Security 7.0, BitDefender Total Security 2008, Panda: Internet Security
  • Operating system languages: Arabic, Bulgarian, Catalan, Chinese (Simplified), Chinese (Traditional), Croatian, Czech, Danish, Dutch, English-UK, English-US, Estonian, Filipino, Finnish, French, German, Greek, Hebrew, Hindi, Hungarian, Indonesian, Italian, Japanese, Korean, Latvian, Lithuanian, Norwegian, Polish, Portuguese (Portugal), Portuguese (Brazil), Romanian, Russian, Serbian, Slovak, Slovenian, Spanish, Spanish (Latin America), Swedish, Thai, Turkish, Ukrainian, Vietnamese

Report a bug