Last year, a similar app crashed the night before the CPS 2231 midterm. StudyBuddy must survive the same night: about 600 active students, up to 300 concurrent, many asking Buddy the same questions.
Write a system test plan (about one page) with:
- Objectives and requirements under test (link to measurable requirements: response-time percentiles, availability, error rate, Buddy fallback).
- Workload model — which user actions, in what proportions, and the target throughput (show a Little's-law calculation).
- Test types — load, stress, soak (and what "pass" means for each).
- Environment and data — where the test runs, test accounts, what must not be used (real student data, the paid AI provider at full scale?).
- Monitoring — what you measure on servers and in the app.
- Exit criteria and what you will do if it fails.