Iím trying to come up with a solution for our web releases of our software. Just a little background, we have a client server operation that has been implemented into the web. Like everyone else! The web application uses pieces of the server code to operate, acting as the client. So the problem that I run into is that the server code never matches the web client code, and to make things even worse we have different web code trails to different clients. It used to be that way with the server code, but thatís why they hired me and a few other QA Engineers! Iím having trouble with the web code though because we allow the client to configure the look and feel of there own web site, that way they donít look the same as there competitors. This is great but each client has the preference files configured differently. Upgrades to the client boxes arenít easy, generally they have asked for enhanced features that give options to configure the site. Iím looking for ideas that would allow me to release the web code with the GUI and server code on the scheduled release dates for all clients. Hopefully this isnít confusing and someone out there has some good ideas for me.
Thanks and Enjoy
Re: Web Releases
It seems like one approach might be to test the core product (the base patterns) by itself. It sounds like you are saying the server has a set of functionality it can provide to the clients and then different configurations use different sets of the functions. Either using a client configuration that exercises all of the functions or a driver test client, you can test all of the server functionality. Then, for each client configuration implemented, you can focus more on the interface to the server, user interface design, and other client specific issues.
[This message has been edited by testgeek (edited 05-09-2002).]