A new SaaS timecard application that is being tested will be used by all employees at a large corporation. The following process was used to test the application: 1. Three users from each site used…

High availability validation requires testing failover scenarios, uptime under simulated failures, and redundancy mechanisms, none of which were included in the described testing process.

Three weeks of live usage by real users under actual workloads allowed testers to observe response times and throughput, directly validating whether the application meets performance requirements.

Connectivity testing involves verifying network path accessibility, port availability, and protocol compatibility from various endpoints or device types, which this plan did not address.

Comparing outputs of the old and new applications side by side is a classic parallel testing technique specifically designed to confirm that the new system produces accurate and consistent results, validating data integrity.

Selecting three users from each site across a large multi-site corporation provides representative load data to determine whether the application scales to the organization's full size and geographic distribution, confirming sizing requirements.

Security testing requires dedicated activities such as vulnerability scanning, penetration testing, or access control audits, which were entirely absent from the described testing steps.