Forum Discussion
EADS_Support
16 years agoOccasional Contributor
Hi Ole
thanks for the response, the change to the memory settings has improved things slightly (I can up the row count by another few k now) but it still falls over apparently in the same way
unfortunately due to corporate policy I can't send out the project, the groovy script that is run however is as follows
simple test case setup with the following steps
data source
soap req
groovy script
property trans
data loop
the service invoked is quite involved with approx 125 seperate elements, the data set created to test has been produced using the PICT pairwise tool whilst trying to get as high a coverage of data configurations as possible, this has however produced just under 19k rows of data hence the issues encountered
Regards
Mike
thanks for the response, the change to the memory settings has improved things slightly (I can up the row count by another few k now) but it still falls over apparently in the same way
unfortunately due to corporate policy I can't send out the project, the groovy script that is run however is as follows
//## define current test case
def testCase = testRunner.testCase
//log.info "Test case: $testCase?.name"
//## loop through steps within test case
def int i = 1
testRunner.results.each
{
testResult->
//## define current test step name
def testStepName = testResult?.testStep.name
//## check to see if the step is the one required for reporting
if (testStepName == "SoapRequestTestStepName")
{
//log.info "Test step '$testStepName' result: status $testResult.status, Time Taken: $testResult.timeTaken (ms)"
//## define data sink to use and then output to data sink elements named below
def dataSink = testRunner.testCase.testSteps['DataSink']
dataSink.setPropertyValue('TestStepName', testStepName)
dataSink.setPropertyValue('TestStepStatus', testResult?.status)
dataSink.setPropertyValue('StepTimeTaken', testResult?.timeTaken)
}
++i
}
simple test case setup with the following steps
data source
soap req
groovy script
property trans
data loop
the service invoked is quite involved with approx 125 seperate elements, the data set created to test has been produced using the PICT pairwise tool whilst trying to get as high a coverage of data configurations as possible, this has however produced just under 19k rows of data hence the issues encountered
Regards
Mike