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…

Testing with only "three users from each site" for three weeks does not adequately simulate the load or failure scenarios required to confirm high availability for "all employees at a large corporation."

Using the application for three weeks by "three users from each site" and "side by side with the existing application" allows for observing response times and overall user experience under typical loads, confirming performance characteristics.

While users accessed the application, the described testing does not specifically focus on confirming network connectivity robustness or troubleshooting, but rather on application functionality and output.

"The outputs of the old and new applications were compared side by side" directly validates that the new application processes data correctly and produces accurate results, thereby confirming data integrity.

Testing with a small, distributed user base over a period of weeks, while observing behavior and comparing outputs, helps inform initial sizing requirements by indicating if the application can handle expected transaction volumes and data for that subset, relative to a known baseline.

The described testing process does not include any specific steps for vulnerability scanning, penetration testing, or access control validation to confirm security.