Tips for Automated Testing of New Software Product Releases, Part II

To parameterize or not to parameterize?

When designing and building TestComplete automated test scripts, it is a generally accepted best practice that you should replace any static input values with dynamic parameters. For example, if you record a "login" script, you should ensure that the username is a TestComplete parameter into which different values can be passed. This is an important strategy for ensuring your test scripts stand the test of time, and making it possible to reuse your scripts in a variety of different use cases.

However, there may come a time when you should not parameterize. Why, you might ask, would I suggest that you compromise the long term flexibility and sustainability of your test scripts?

The answer is speed. If you have a release that you need to test ASAP, and if you plan to introduce a major application redesign within the next few months, than you should optimize your script development efforts for speed rather than for flexibility and sustainability. By minimizing the amount of post-script enhancement work that needs to be done, it is possible to rapidly create an expansive test suite that can be used effectively for your short-term testing needs. These scripts can then be thrown away, and replaced with a different set of scripts for the redesigned application.

The bottom line is that your TestComplete script development strategy should align to your testing objectives and application release strategy.

To learn more about WinMill Software's application development best practices and how we help make your project a success, contact us at inquiry@winmill.com or (888) 711-6455.