[GitHub] brooklyn-server issue #277: Fix TestCases, and add TestSensor.abortCondition...

[neykov <gi...@git.apache.org>]

Github user neykov commented on the issue:

    https://github.com/apache/brooklyn-server/pull/277
  
    After a very quick look I think that's very useful and something I felt the need for. When previously thinking about the problem the approach I came up with is having `validConditions` instead of `abortConditions`. This way you only define the expected states the blueprint will go through instead of any combination of invalid state. For `service.state` that would usually be `STARTING`, `RUNNING`, but where it becomes even more useful is asserting on any random sensor. For example resizing a cluster and asserting the new size - the expected sizes are the initial one and the end one. Using the `abortConditions` here would not be too practical.
    Or may be both are useful - would be easier to use one or the other for different use cases.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---