Lawl ... sometimes people dig themselves holes so deep, so fast, that you could never come close if you tried.

But yes, as per all the comments after yours that make you look like a douche, you can indeed stress test anything. For us, we knew 3v3/4v4 games worked just fine, but we wanted to push the engine to it's limit of 6v6 (it is actually 7v7 but we want two team computers) ... and we did indeed find that it came under pressure at that capacity. Thanks to some kind nudges in the right direction, I figured out how to double the performance of the engine by changing a single line (for myself going from 25fps to 50fps in 2560x1440 extreme). So it was indeed worth while, and we would have never found that out without pushing the engine to it's limit, even if we decide to limit the amount of players later on.

Actually you're wrong, stress testing is not only about servers... In this case I think they meant stress testing how the map handles the triggers actions and data effects/events, when there are lots of players ingame... Because whoever already published a map on Bnet knows how much of a pain in the you-know-what it is when it lags when something is not coded right. You can't realize how bad a map is before you really put it to the test with lots of players doing completely silly and unexpected stuff.