If you don't know the exact cause of why the connections dropped, or a reliable way of reproducing it, or empirical data of how often it happens under what kinds of conditions, then you can't hope to employ a script or other test tool that will give you any meaningful results.
For example, if you, without evidence, assumed the problem happened while a lot of data was flowing, you might write a script or run a tool to send/receive a lot of data continuously. But if the original problem was actually a bug in how the device handles power-save mode during idle periods, your traffic-sending tool would actually prevent the real problem from happening by keeping the link from ever going idle. So you'd run your tool and think the firmware update fixed it, when it hadn't.
have you tried a different channel and lower speed settings? – Uğur Gümüşhan – 2015-04-04T22:04:21.097
try the ping-t command (equivalent in Unix) to ping the wireless router and collect empirical data in the first place. By repeating the same experiment over and over again for "N" number of times - you will be able to find out the difference – Prasanna – 2015-07-06T02:41:49.310