Load testing is employed to determine if your system (application) and servers (website) are equipped to handle the network traffic anticipated at deployment, as well as increased network traffic in the future.

What happens when your server or web site is hit by a large number of users at the same time? Will it still function as intended? The basic purpose of load and performance testing an application and/or website is to accomplish the following:

• To measure the effects on user experience as total user load is increased
• To measure the average page response time and determine if the performance is acceptable at both average and maximum user loads
• To quantify the upper limit of the hardware being accessed by the application to determine whether the current system is capable of handling the anticipated future loads

Lyte Technologies will employ sophisticated load testing tools to put stress on your servers. In 2004, we launched our performance engineering improvement strategy initiative. We became trained and certified in two of the nation leading stress testing tools, which can orchestrate hundreds of thousands of tasks/virtual users and apply a significant (literally thousands of users) to a network to provide a strong load for best performance testing analysis. Many companies can’t afford to do large-scale testing – and we provide a solution for them. We will establish the maximum performance limits of your application, as well as uncover any unexpected problems that may occur during heavy usage.

Our unit testing team focuses on the verification effort of the smallest unit of software design of the software component or module. Using the component level design description as a guide, important control paths are tested to uncover errors within the boundaries of the module. We are aware of the relative complexity of tests and the errors those tests uncover which is limited by the constrained scope established for unit testing. Our unit testing focuses on the internal processing of software logic and data structures within the boundaries of a component.

Our integration testing is a systematic technique for constructing the software architecture while at the same time conducting tests to uncover errors associated with the interfacing. Our goal is to take unit tested components and build a structure that has been dictated by design.

Our recovery testing is designed to force a system to fail in a variety of ways and verifies that the recovery process is properly performed. If recovery is automatic (performed by the system itself), reinitialization, check pointing mechanisms, data recovery, and restart are evaluated for correctness. If recovery requires human intervention, the mean-time-to-repair (MTTR) is evaluated to determine whether it is within acceptable limits.