reports/extensions.st
author Jan Vrany <jan.vrany@fit.cvut.cz>
Fri, 06 Jun 2014 10:29:27 +0200
changeset 237 8229efa1f621
parent 161 272aec4b1764
child 529 d000086cab5e
permissions -rw-r--r--
Dump all threads when testcase times out. This could help to identify a reason for timeout, i.e., whether the testcase takes a long time or if it got stuck is some kind of deadlock.

"{ Package: 'stx:goodies/builder/reports' }"!

!TestCase methodsFor:'accessing'!

nameForHDTestReport

    ^(self class package asString replaceAll: $: with: $.; replaceAll: $/ with: $.) , '.' , self name

    "
        Object nameForHDTestReport    
        SVN::Repository nameForHDTestReport
    "

    "Created: / 01-04-2011 / 16:09:46 / Jan Vrany <jan.vrany@fit.cvut.cz>"
    "Modified: / 06-04-2011 / 13:36:39 / Jan Vrany <jan.vrany@fit.cvut.cz>"
! !

!TestCase methodsFor:'accessing'!

selectorForHDTestReport

	^testSelector

! !

!TestCase methodsFor:'accessing'!

timeout
    "Returns a default timeout (sec) for the test.
     If nil is returned, no timeout enforced.

    Note that the timeout is set only when running under
    report runner, interactive tools does not use it"

    | method |
    method := self class lookupMethodFor: testSelector.
    method annotationsAt:#timeout: do:[:annotation|
         ^annotation arguments first
    ].
    ^60"sec - default timeout"

    "Created: / 12-01-2012 / 17:48:25 / Jan Vrany <jan.vrany@fit.cvut.cz>"
    "Modified: / 26-04-2013 / 16:58:17 / Jan Vrany <jan.vrany@fit.cvut.cz>"
! !

!TestCase class methodsFor:'testing'!

isJUnitTestCaseProxy

	^false

! !

!TestCase class methodsFor:'testing'!

isTestletTestCaseProxy

	^false

! !

!stx_goodies_builder_reports class methodsFor:'documentation'!

extensionsVersion_CVS
    ^ '$Header$'
! !