Glavs Blog

Well, as you may know from the previous entries, we were due to enter performance testing for a project I have been designing and working on. Unfortunately, what was once a nice and harmonious relationship with the client has now turned a bit sour as we did not enter UAT (User acceptance testing) by the due date. Initially we missed by one day with some known problems in the system that we were working to fix. Unfortunately, the client has used this as leverage to put the pressure on and now we are backtracking to get everything requested and have been  falling further behind (we are now almost a week behind). Performance testing has been shelved for the time being not only because we were behind, but also due to infrastructure and other issues beyond our direct control. So I can't report to you how wonderfully stable and resilient our application is at hundreds of concurrent users :(

In a project I have been designing and working on lately, we are almost about to finish system testing and enter UAT (user acceptance testing). Its nice to be able to see something you have designed really start to work as intended, but what I find most interesting right about now is that we are also about to do some performance testing. Its good to see your design doing what it was intended to do, but what can it *really* do when you put the "pedal to the metal"?