Ticket #210 (closed defect: fixed)
Step transaction logging for TG4W and soapUI ScriptRunners
| Reported by: | fcohen | Owned by: | |
|---|---|---|---|
| Priority: | critical | Milestone: | verify |
| Version: | 5.2 | Keywords: | |
| Cc: |
Description (last modified by fcohen) (diff)
A functional test TestScenario using the TestGen4Web or soapUI ScriptRunner currently records the operation of the test as a single step transaction. For instance:
<test>
<run module="JythonModule" name="TestGen4WebTest"
testclass="HTMLTest" method="test" langtype="jython"/>
</test>
The resulting transaction log file looks like this:
<testcase size="1" description="TG4W_usecase" cvus="2">
<transaction cvus="2" threadid="1" sequence="TG4W_sequence" duration="30"
error="" nodename="localhost" result="true" timestamp="1202871643677"
totaltime="238" >
</transaction>
...
With <step> logging enabled the transactional log must log the steps operated within the ScriptRunner. For instance, the TestGen4Web ScriptRunner will add <step> entries to the transaction log for each recorded GET/POST operation.
<testcase size="1" description="TG4W_usecase" cvus="1">
<transaction cvus="1" threadid="0" sequence="TG4W_sequence" duration="30" error=""
nodename="localhost" result="true" timestamp="1202875643247" totaltime="311">
<step id="0" name="MyTest" totaltime="106"/>
<step id="1" name="MyTest" totaltime="106"/>
<step id="2" name="MyTest" totaltime="99"/>
</transaction>
-Frank
Change History
Note: See
TracTickets for help on using
tickets.
