| || |
testing client server based application
The application i am working, works on client side only with a license. i.e. if the license server is off then the application of client side will not be able to work.
I am new to testing such things. Can anybody list some of the possible test cases for such a case.
One thing, among several things i have tried, is:
when the license server is closed then the application is closed on client side after the client checks after random period of time for server status and does not find the server on.
thanks in advance [img]images/icons/smile.gif[/img]
Re: testing client server based application
so, the context of this is, that the application under tests this needs to retrieve a license and hold a license from a server to work on the client side? Is it only if the server is Off that it will not find the licence as the original question propose?
Some other possible tests then,assuming it is not only find if server is on as the criterion used are:
loss of connection to server during operation and observing the effect, a connection to an invalid licence (it has expired, is not properly installed, is not authenticated), attempting to grab a licence whilst none are "free", operating with multiple instances of the client side application, issues with authentication of the licence(hanshake issues)and depending on how of the system ensures the connection is inplace you can do some non functional tests on the security (WEP keys?), on the encryption of the licence, on the bandwidth the open licence connection takes, the releasind (or not) of the licence at the end of each sessions, how long will the system operate with a "lost" licence session, will the system reconnect post loss of session to the same session/ a new session/ will not reconnect as session hangs after loss?