This is probably the most difficult question I've had to answer this week. I can't think of any 1 specific feature that I like the most. GenRocket has blood, sweat, and tears entrenched all through the code. If I were to talk about one feature that wasn't really mentioned during the week, I think it would probably be Resources.
Several of our Receivers require a physical path to some location and/or file on the machine that is running the Scenario. XMLFileReceiver, for example, needs to know where to write the XML file to. If you were to put an absolute path to a location on your computer, and then Sara tried to run the same Scenario on her computer, it might fail for her depending on the path. So instead of hard coding the path, you would define a Resource. You might create a Resource called 'output.dir'. Then, both you and Sara would go to the My Resources section of the app, and tell GenRocket what that Resource should be
Then, when you need the path for your Receiver, you would reference the Resource.
Now, when the Scenario is built, it will contain the Resource path for the user who downloaded it. Each user can then run the same Scenarios on their respective computers and servers.
That's interesting, Gregg. Thanks for sharing it with us.
I just checked GenRocket's website again. I remember seeing a chart that displayed what features were supported by different type of subscriptions, but I can't see it now. Has it been removed? I also remember seeing something on cloud testing, but I'm not sure. I can't find any of that information on the website now. Does GenRocket have support for cloud testing?