What is the mechanism by which JBlitz captures test configurations ?
Unlike more expensive tools that record and playback web conversations, we have opted for a simpler approach to capturing test configurations. This approach is based on the assumption that the developer or test engineer knows which key resources and scenarios are the most appropriate to test. Thus, JBlitz allows the engineer to input precisely the resources and parameters to be used at each point in the test. This approach also avoids the need to learn proprietary and complicated scripting languages that other tools often demand. Of course, realistic testing involves taking the specified test URLs and varying the parameters passed to the web server with each request. JBlitz does this via ‘dynamic substitutions’. These are specified as ‘%’ substitution elements embedded in the URLs. JBlitz substitutes values for these elements at test time according to well specified rules.
