| Issue 46: | Create an aggregate factor/threshold of test results in the MXUnit Ant Task | |
| 1 person starred this issue and may be notified of changes. | Back to list |
The concept behind this feature would be to return or set a property that Ant can use to conditionally process events. Currently, the Ant task prints test results, but this would set a specific number or factor, or set of data that we could use to determine if we want to further process tests or other targets within Ant. For example, if we wanted to perform an automated deployment in Ant, but only in the case where there were no errors or no failures. So, in the build file we would first run all the tests, and then only deploy the software if the tests meet or exceed a certain threshold. It might be something like 100% [OK], 100% [error free], 89.2% [failure free]. And then we could use that/those conditions to process further. It's not clear how we can persist this over multiple tests ... or how we can set and increment data in the Ant context ...
Jan 14, 2008
Project Member
#1
marc.es...@gmail.com
Jan 24, 2008
Update: Got this persisted in the ant task instance and is printing to stdout ok. I was thinking of simply writing the info to a properties file that ant could read in a task. But I seem to recall that ant loads all properties first ... we'll see later today. Boss want a demo of accelerated deployment with flagging of test results.
Feb 11, 2008
Got the properties thing working and then also added haltonerror and haltonfailure, which actually makes a bit more sense.
Status:
Fixed
|