Anyone else notice that .pln test runs are considerably slower than identical .t runs?
As an example, a .pln run takes over 2 hours; a .t run only 1.5 hours - 25% less time.
Has anyone discovered why?
Looking this from Resource Management angle Externally, i beleive additional number of process initiated while running the testcase from .pln file
1. While running the .pln
a. It should save the .pln and take a back up of it as ".pl_"
b.It needs to locate the .t and the testcase specified in the testplan
c.Followed by it should invoke .t
2. While running .t
a. It needs to save, compile and back up the .t file
b. Run the .t File
Even though there is resource consumption, running from the .pln has it's own advantage.
The time and memory Consumption depends on the testcase size and its coverage.
I am not sure about other internal threads spawned by silktest to do these process.
I have never noticed this point but it may also be due to checking whether a case in .pln file is marked for execution or not. Just a guess.
"A highly advanced bug is indistinguishable from a feature."
A highly advanced bug is indistinguishable from a feature.