Thanks David.
Paul replied to a support request this morning about this and was able to replicate. I'll post his note below so that others can benefit:
Hello Stephen,
I have reproduced the problem. When running a test with an optional parameter with a specified default value, the test run results will be different depending on the way you are running the test:
- when running the test from within the Project Explorer, the test is run with an undefined parameter value;
- when running the test from within the Keyword Test editor, from script or as a test item, the test is run with the specified default value.
I have registered this issue in our database. Currently, to avoid the problem, do not run keyword tests from within the Project Explorer. You can find possible ways to run a keyword test in the "Running Keyword Tests" (
http://www.automatedqa.com/support/viewarticle/12564/ ) help topic.
Best regards,
Paul
