You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alan Conway (JIRA)" <qp...@incubator.apache.org> on 2007/01/03 22:06:27 UTC
[jira] Created: (QPID-242) Cross language testing
Cross language testing
----------------------
Key: QPID-242
URL: https://issues.apache.org/jira/browse/QPID-242
Project: Qpid
Issue Type: Bug
Components: C++ Broker, C++ Client, Java Broker, Java Client
Reporter: Alan Conway
We need to test between different language clients & servers. To this end I suggest the following framework:
For each broker impl X, add script to qpid/bin/broker_X where X is cpp, java etc. with the following behavior:
broker_X start [port] # start the broker on port (defaults to AMQP port)
broker_X stop [port] # stop the broker on port.
Each implementation then should run its client tests against other brokers using these scripts to start & stop the foreign brokers.
IMPORTANT: Once X has been built in a clean working copy, the broker_X script shoud work.
The broker_X script MUST NOT make any assumptions about environment variables or current directory. The script can use $0 to find the qpid/bin directory. It can assume that:
- $0 is the qpid/bin directory
- $0/../X has been built already.
The scriptmust set up all required env vars, any config files etc. that are not automatically created by building X.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (QPID-242) Cross language interop testing
Posted by "Gordon Sim (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gordon Sim closed QPID-242.
---------------------------
Resolution: Duplicate
Appears to be a duplicate of QPID-467.
> Cross language interop testing
> ------------------------------
>
> Key: QPID-242
> URL: https://issues.apache.org/jira/browse/QPID-242
> Project: Qpid
> Issue Type: Test
> Components: C++ Broker, C++ Client, Java Broker, Java Client
> Reporter: Alan Conway
> Priority: Critical
> Fix For: M2
>
>
> We need to test between different language clients & servers. To this end I suggest the following framework:
> For each broker impl X, add script to qpid/bin/broker_X where X is cpp, java etc. with the following behavior:
> broker_X start [port] # start the broker on port (defaults to AMQP port)
> broker_X stop [port] # stop the broker on port.
> Each implementation then should run its client tests against other brokers using these scripts to start & stop the foreign brokers.
> IMPORTANT: Once X has been built in a clean working copy, the broker_X script shoud work.
> The broker_X script MUST NOT make any assumptions about environment variables or current directory. The script can use $0 to find the qpid/bin directory. It can assume that:
> - $0 is the qpid/bin directory
> - $0/../X has been built already.
> The scriptmust set up all required env vars, any config files etc. that are not automatically created by building X.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (QPID-242) Cross language interop testing
Posted by "Rupert Smith (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472241 ]
Rupert Smith commented on QPID-242:
-----------------------------------
It might also be worthwhile having a broker_X ping (or test or isAlive) script too. This would be for build automation purposes, so a script can start a broker then repeatedly test to check when is is 'live' before running tests through it.
Also need to add requirement that scripts never fail to run when a broker becomes unresponsive, but timeout instead. This is that these scripts do not fail to run during an automated build.
Need to fully interop test between clients in different languages, not just brokers. So X clients and Y brokers, means X times Y times X combinations of producers, brokers and receivers to cycle through all test combinations. I think this spec should be expanded a bit to include defintion of scripts for starting test clients too. Should specify exactly how these test clients should behave, what exchanges, virtual hosts, queue names etc. they send to. Nothing to complex, just a fairly minimal spec and uniz scripts to run everything. Will post about this proposal on the dev list sometime soon.
> Cross language interop testing
> ------------------------------
>
> Key: QPID-242
> URL: https://issues.apache.org/jira/browse/QPID-242
> Project: Qpid
> Issue Type: Test
> Components: C++ Broker, C++ Client, Java Broker, Java Client
> Reporter: Alan Conway
>
> We need to test between different language clients & servers. To this end I suggest the following framework:
> For each broker impl X, add script to qpid/bin/broker_X where X is cpp, java etc. with the following behavior:
> broker_X start [port] # start the broker on port (defaults to AMQP port)
> broker_X stop [port] # stop the broker on port.
> Each implementation then should run its client tests against other brokers using these scripts to start & stop the foreign brokers.
> IMPORTANT: Once X has been built in a clean working copy, the broker_X script shoud work.
> The broker_X script MUST NOT make any assumptions about environment variables or current directory. The script can use $0 to find the qpid/bin directory. It can assume that:
> - $0 is the qpid/bin directory
> - $0/../X has been built already.
> The scriptmust set up all required env vars, any config files etc. that are not automatically created by building X.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-242) Cross language interop testing
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-242:
--------------------------------
Fix Version/s: M2
> Cross language interop testing
> ------------------------------
>
> Key: QPID-242
> URL: https://issues.apache.org/jira/browse/QPID-242
> Project: Qpid
> Issue Type: Test
> Components: C++ Broker, C++ Client, Java Broker, Java Client
> Reporter: Alan Conway
> Fix For: M2
>
>
> We need to test between different language clients & servers. To this end I suggest the following framework:
> For each broker impl X, add script to qpid/bin/broker_X where X is cpp, java etc. with the following behavior:
> broker_X start [port] # start the broker on port (defaults to AMQP port)
> broker_X stop [port] # stop the broker on port.
> Each implementation then should run its client tests against other brokers using these scripts to start & stop the foreign brokers.
> IMPORTANT: Once X has been built in a clean working copy, the broker_X script shoud work.
> The broker_X script MUST NOT make any assumptions about environment variables or current directory. The script can use $0 to find the qpid/bin directory. It can assume that:
> - $0 is the qpid/bin directory
> - $0/../X has been built already.
> The scriptmust set up all required env vars, any config files etc. that are not automatically created by building X.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-242) Cross language interop testing
Posted by "Alan Conway (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Conway updated QPID-242:
-----------------------------
Priority: Critical (was: Major)
> Cross language interop testing
> ------------------------------
>
> Key: QPID-242
> URL: https://issues.apache.org/jira/browse/QPID-242
> Project: Qpid
> Issue Type: Test
> Components: C++ Broker, C++ Client, Java Broker, Java Client
> Reporter: Alan Conway
> Priority: Critical
> Fix For: M2
>
>
> We need to test between different language clients & servers. To this end I suggest the following framework:
> For each broker impl X, add script to qpid/bin/broker_X where X is cpp, java etc. with the following behavior:
> broker_X start [port] # start the broker on port (defaults to AMQP port)
> broker_X stop [port] # stop the broker on port.
> Each implementation then should run its client tests against other brokers using these scripts to start & stop the foreign brokers.
> IMPORTANT: Once X has been built in a clean working copy, the broker_X script shoud work.
> The broker_X script MUST NOT make any assumptions about environment variables or current directory. The script can use $0 to find the qpid/bin directory. It can assume that:
> - $0 is the qpid/bin directory
> - $0/../X has been built already.
> The scriptmust set up all required env vars, any config files etc. that are not automatically created by building X.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (QPID-242) Cross language interop testing
Posted by "Alan Conway (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Conway updated QPID-242:
-----------------------------
Summary: Cross language interop testing (was: Cross language testing)
> Cross language interop testing
> ------------------------------
>
> Key: QPID-242
> URL: https://issues.apache.org/jira/browse/QPID-242
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker, C++ Client, Java Broker, Java Client
> Reporter: Alan Conway
>
> We need to test between different language clients & servers. To this end I suggest the following framework:
> For each broker impl X, add script to qpid/bin/broker_X where X is cpp, java etc. with the following behavior:
> broker_X start [port] # start the broker on port (defaults to AMQP port)
> broker_X stop [port] # stop the broker on port.
> Each implementation then should run its client tests against other brokers using these scripts to start & stop the foreign brokers.
> IMPORTANT: Once X has been built in a clean working copy, the broker_X script shoud work.
> The broker_X script MUST NOT make any assumptions about environment variables or current directory. The script can use $0 to find the qpid/bin directory. It can assume that:
> - $0 is the qpid/bin directory
> - $0/../X has been built already.
> The scriptmust set up all required env vars, any config files etc. that are not automatically created by building X.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (QPID-242) Cross language interop testing
Posted by "Alan Conway (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Conway updated QPID-242:
-----------------------------
Issue Type: Test (was: Bug)
> Cross language interop testing
> ------------------------------
>
> Key: QPID-242
> URL: https://issues.apache.org/jira/browse/QPID-242
> Project: Qpid
> Issue Type: Test
> Components: C++ Broker, C++ Client, Java Broker, Java Client
> Reporter: Alan Conway
>
> We need to test between different language clients & servers. To this end I suggest the following framework:
> For each broker impl X, add script to qpid/bin/broker_X where X is cpp, java etc. with the following behavior:
> broker_X start [port] # start the broker on port (defaults to AMQP port)
> broker_X stop [port] # stop the broker on port.
> Each implementation then should run its client tests against other brokers using these scripts to start & stop the foreign brokers.
> IMPORTANT: Once X has been built in a clean working copy, the broker_X script shoud work.
> The broker_X script MUST NOT make any assumptions about environment variables or current directory. The script can use $0 to find the qpid/bin directory. It can assume that:
> - $0 is the qpid/bin directory
> - $0/../X has been built already.
> The scriptmust set up all required env vars, any config files etc. that are not automatically created by building X.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira