ContributionsMost RecentMost LikesSolutionsRe: Test Variables The usefulness of properties come from many tests being able to access the same property, so rather than changing the value many times for each request that uses it, you can change the property value and all the requests that access it use the new updated value. Properties on a TestStep level are not very useful, as you can hard-code the value straight into the request. As no other TestSteps would have access to properties defined at a TestStep level, there is no value of using a property rather than physically specifying the value directly in the request. Re: POI getCell() with missing cell policy returning null pointer exception Although i didn't get a response, i found a work around i thought i would share. I think the issue is that, although it doesn't throw an error, the getCell MissingCellPolicy isn't fully supported by the compiler SOAPUI OS uses. I used a combination of using the MissingCellPolicy and exception handling via nested try/catch statements to be able to achieve what i needed. SOAPUI OS TestSuite Log Export To File Hello, There is an "Exports this log to a file" button on the TestSuite editor window, above the TestSuite log. I am looking to automate this function from the TestSuite teardown script. Is there a way to simply piggyback on the existing functionality by calling a method and passsing it the path i wish to save the log at? Thanks in advance! POI getCell() with missing cell policy returning null pointer exception Hello, I am trying to create a groovy script to read from an excel sheet using Apache poi. To handle null pointer exceptions when calling getCell(), i am calling it with the MissingCellPolicy CREATE_NULL_AS_BLANK, however, it is still triggering a null pointer exception. I have attached a screenshot of my code. Any assistance to help resolve this issue would be appreciated. Solved