During tests we wait for PIT to end before checking the UI. If PIT runs for too long, we timeout and throw an error (shouldn't happen: just a protection against infinite loops). Currently, the timeout is based on SWTBot's timeout property. Because of that, changing the timeout for PIT also changes the timeout when searching for UI elements through SWTBot. We want to be able to change those two timeouts independently:
SWTBot's timeout is already configurable through the org.eclipse.swtbot.search.timeout property. I propose to create a new property, e.g., org.pitest.pitclipse.tests.pit.timeout, that holds the timeout for PIT.
Motivation
During tests we wait for PIT to end before checking the UI. If PIT runs for too long, we timeout and throw an error (shouldn't happen: just a protection against infinite loops). Currently, the timeout is based on SWTBot's timeout property. Because of that, changing the timeout for PIT also changes the timeout when searching for UI elements through SWTBot. We want to be able to change those two timeouts independently:
Discussion raised in https://github.com/pitest/pitclipse/pull/175#discussion_r688609291.
Proposed Solution
SWTBot's timeout is already configurable through the
org.eclipse.swtbot.search.timeoutproperty. I propose to create a new property, e.g.,org.pitest.pitclipse.tests.pit.timeout, that holds the timeout for PIT.