PERFORMANCE ENGINEERING IT IS!
We are followers of Scott Barber and we understand Web Load Testing / Stress Testing / Front-end Performance Testing well enough. We understand HTTP requests and headers, their sizes, caching and all minute things that impacts performance of your web app. We observe the behavior of the application very carefully and monitor the logs. And that is why we call “Performance Engineering”.
We run lots of iterations before we come to a conclusion and here is a sneak peek into a part of what we do in performance testing for applications.
- Bandwidth related tests
- Web-page load with cache
- Web-page load without cache
- Identifying possible bottlenecks
- Identify the key scenarios
- Design test data for every test that we do
- Simulate user variances
- And more
OPEN SOURCE AND COMMERCIAL TOOLS
We respect tools as they aid in implementing our ideas, but mind-set is first and then tools (A fool with a tool is still a fool ~ Marshal McLuhan). We employ open-source tools or commercial tools based on the need that we have. Why open-source? Because we have the flexibility in changing the code to suit our needs and as we have in-house hard-core developers, it will not be difficult for us to tweak the tool to suit our performance testing needs. Why commercial? Because "Context is the king" and we consider time, efforts, budget attributes to decide whether we need to go with open-source / freeware or commercial tools? We value both open-source and commercial tools when it comes to performance testing or load testing or stress testing or volume testing.