Win7 x64
Ranorex 5.0.1
Not sure if this is a bug, or intended, but wanted to get clarification.
If I am running a test and hit the interruption key (Pause in my case), the test's teardown regions are not being executed. (NOTE: This is only for manual interruptions, normal stops on error or test completion DO run the teardown regions correctly.) In my case it is a Suite-level teardown region (haven't tried it with a Case-level teardown), don't know if this makes a difference.
There is nothing in the documentation that says this is intentional for a manual interruption, so my assumption is that this is a bug, but I can also see how it might be intended.
Thanks guys!
BUG?: Teardown sections not run on manual test interuption
BUG?: Teardown sections not run on manual test interuption
Shortcuts usually aren't...
- Support Team
- Site Admin
- Posts: 12167
- Joined: Fri Jul 07, 2006 4:30 pm
- Location: Graz, Austria
Re: BUG?: Teardown sections not run on manual test interuption
Hello krstcs,
The abort key is definitely designed to stop the test execution (teardown section included). Therefore, the experienced behavior is intended. It empowers the user to manually stop the test execution.
Regards,
Robert
The abort key is definitely designed to stop the test execution (teardown section included). Therefore, the experienced behavior is intended. It empowers the user to manually stop the test execution.
Regards,
Robert
Re: BUG?: Teardown sections not run on manual test interuption
Thanks Robert. That's what I thought, but since it isn't specifically stated I wanted to make sure.
Perhaps that should be included as a note in the user guide?
Perhaps that should be included as a note in the user guide?
Shortcuts usually aren't...
- Support Team
- Site Admin
- Posts: 12167
- Joined: Fri Jul 07, 2006 4:30 pm
- Location: Graz, Austria
Re: BUG?: Teardown sections not run on manual test interuption
Hi krstcs,
Thank you for reporting. I've added an entry in our bug tracking system and we will discuss this internally.
Kind regards,
Markus (S)
Thank you for reporting. I've added an entry in our bug tracking system and we will discuss this internally.
Kind regards,
Markus (S)