Web site load testing application at eBSuccess
As software architect, I designed and architected a web-server load-testing suite of software, and I wrote the core application in the suite. This was heavily multithreaded (100’s of threads), was the most efficient of it’s kind (at the time, at least), and was easily reconfigured for a server farm after I left.
It was very modular:
- Each “script” was a Java class that was auto-generated when one recorded a “user experience” using a web browser plugin (written by someone else). Java, being a non-proprietary language, was then easily edited by developers.
- The program then loaded the chosen “user experiences” as Java classes, compiled them on the fly using just-in-time compiling, and then ran the “user experiences” at full speed.
- For web-site testers editing the “user experiences”, I built a library for easy information extraction from HTML. That enabled them to easily search for links, in grids, buttons, etc.
Testers could also edit the “user experiences”, to do things like fetch username/password pairs from test databases to test logging in, and other such potentially tricky tasks. - At the time, the Java libraries for HTTP didn’t have hooks for inserting timers for measuring things such as response time, data throughput, etc. So, I had to write a complete HTTP implementation.
- After I left, the team modified my application to run in a server farm. It took them only one day to separate the UI from the business layer, despite never having looked at my code base before. It was then easy for them to make it into server farm executables.
When testing, I tested against a few randomly selected web sites. I was soon blocked from those sites. I presume my software did successful DoS attacks from my laptop, which was only running at 15%.
My sincere apologies.
- Architect
- Database Developer
- Developer
- +2