[jira] [Updated] (QPIDIT-100) Check status of broker between tests

2020-06-19 Thread Kim van der Riet (Jira)


 [ 
https://issues.apache.org/jira/browse/QPIDIT-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-100:

Affects Version/s: (was: 0.1.0)
   0.2.0

> Check status of broker between tests
> 
>
> Key: QPIDIT-100
> URL: https://issues.apache.org/jira/browse/QPIDIT-100
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Improvement
>Affects Versions: 0.2.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Minor
>
> If the broker should stop during a test, the test will continue to try to run 
> all of the tests.  A check should be made between each test that will ensure 
> the broker is still present. Perhaps a check of the PID will suffice.
> Note that for some broker configurations (such as multi-node dispatch router 
> tests), multiple nodes and/or brokers may be present, and all of them must be 
> checked.
> If one or more of the test nodes is missing, the test should immediately 
> terminate with an error message.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org



[jira] [Updated] (QPIDIT-100) Check status of broker between tests

2018-06-20 Thread Kim van der Riet (JIRA)


 [ 
https://issues.apache.org/jira/browse/QPIDIT-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-100:

Fix Version/s: (was: 0.2.0)

> Check status of broker between tests
> 
>
> Key: QPIDIT-100
> URL: https://issues.apache.org/jira/browse/QPIDIT-100
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Improvement
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Minor
>
> If the broker should stop during a test, the test will continue to try to run 
> all of the tests.  A check should be made between each test that will ensure 
> the broker is still present. Perhaps a check of the PID will suffice.
> Note that for some broker configurations (such as multi-node dispatch router 
> tests), multiple nodes and/or brokers may be present, and all of them must be 
> checked.
> If one or more of the test nodes is missing, the test should immediately 
> terminate with an error message.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org



[jira] [Updated] (QPIDIT-100) Check status of broker between tests

2018-02-28 Thread Kim van der Riet (JIRA)

 [ 
https://issues.apache.org/jira/browse/QPIDIT-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-100:

Fix Version/s: 0.2.0

> Check status of broker between tests
> 
>
> Key: QPIDIT-100
> URL: https://issues.apache.org/jira/browse/QPIDIT-100
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Improvement
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Minor
> Fix For: 0.2.0
>
>
> If the broker should stop during a test, the test will continue to try to run 
> all of the tests.  A check should be made between each test that will ensure 
> the broker is still present. Perhaps a check of the PID will suffice.
> Note that for some broker configurations (such as multi-node dispatch router 
> tests), multiple nodes and/or brokers may be present, and all of them must be 
> checked.
> If one or more of the test nodes is missing, the test should immediately 
> terminate with an error message.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org



[jira] [Updated] (QPIDIT-100) Check status of broker between tests

2017-11-07 Thread Kim van der Riet (JIRA)

 [ 
https://issues.apache.org/jira/browse/QPIDIT-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-100:

Fix Version/s: (was: Future)

> Check status of broker between tests
> 
>
> Key: QPIDIT-100
> URL: https://issues.apache.org/jira/browse/QPIDIT-100
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Improvement
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Minor
>
> If the broker should stop during a test, the test will continue to try to run 
> all of the tests.  A check should be made between each test that will ensure 
> the broker is still present. Perhaps a check of the PID will suffice.
> Note that for some broker configurations (such as multi-node dispatch router 
> tests), multiple nodes and/or brokers may be present, and all of them must be 
> checked.
> If one or more of the test nodes is missing, the test should immediately 
> terminate with an error message.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org



[jira] [Updated] (QPIDIT-100) Check status of broker between tests

2017-11-07 Thread Kim van der Riet (JIRA)

 [ 
https://issues.apache.org/jira/browse/QPIDIT-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-100:

Affects Version/s: 0.1.0

> Check status of broker between tests
> 
>
> Key: QPIDIT-100
> URL: https://issues.apache.org/jira/browse/QPIDIT-100
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Improvement
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
> Fix For: Future
>
>
> If the broker should stop during a test, the test will continue to try to run 
> all of the tests.  A check should be made between each test that will ensure 
> the broker is still present. Perhaps a check of the PID will suffice.
> Note that for some broker configurations (such as multi-node dispatch router 
> tests), multiple nodes and/or brokers may be present, and all of them must be 
> checked.
> If one or more of the test nodes is missing, the test should immediately 
> terminate with an error message.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org



[jira] [Updated] (QPIDIT-100) Check status of broker between tests

2017-11-07 Thread Kim van der Riet (JIRA)

 [ 
https://issues.apache.org/jira/browse/QPIDIT-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPIDIT-100:

Priority: Minor  (was: Major)

> Check status of broker between tests
> 
>
> Key: QPIDIT-100
> URL: https://issues.apache.org/jira/browse/QPIDIT-100
> Project: Apache QPID Interoperability Test Suite
>  Issue Type: Improvement
>Affects Versions: 0.1.0
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Minor
> Fix For: Future
>
>
> If the broker should stop during a test, the test will continue to try to run 
> all of the tests.  A check should be made between each test that will ensure 
> the broker is still present. Perhaps a check of the PID will suffice.
> Note that for some broker configurations (such as multi-node dispatch router 
> tests), multiple nodes and/or brokers may be present, and all of them must be 
> checked.
> If one or more of the test nodes is missing, the test should immediately 
> terminate with an error message.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org