When do we need to be performance testing
-
After system testing and application security testing but before deployment to production
-
After application security testing but before acceptance test by the client/end user
-
just before deployment to production
-
after system test
Performance testing should occur after security testing but before user acceptance testing. This order ensures security vulnerabilities are identified first, then performance is validated under realistic load conditions, and finally business functionality is verified with end users before production deployment.
Performance testing is typically scheduled after functional and security testing have validated that the system works correctly and safely, but before the client/end user runs acceptance testing — this way performance issues are caught and fixed while the system is still in the vendor/dev team's hands, and the client only signs off once both functional correctness and performance are confirmed. Doing it only "just before deployment" or "after system test" alone is too vague/late in the lifecycle to fit standard SDLC sequencing, and doing it before security testing (implied by the first option's ordering ambiguity) risks retesting performance after security-driven code changes.