For tests specific to a client API, the logical place would be
within the client project. They should be able to be used as
regression tests for that client whenever it is built. I don't know
what test frameworks are used in the Eclipse community, they might
be client language specific too (JUnit for Java for example).
I also envisage there would be tests or test descriptions which will
be applicable in general, either to the MQTT protocol, or servers,
at the packet level. These sorts of tests should be in a separate
testing project I think.
I'm all for contributing as much test material as we have, unless
the volume is totally overwhelming. Rationalization could be done
as needed. On the other hand, test material needs to be documented
pretty well so that other people using it can understand what
defects in might find, and how to fix them, so just contributing
throw-away tests will probably not be productive, neither for the
committers nor users.
Ian Craggs
On 14/06/12 08:04, Nicolas DEVERGE wrote:
yeah, you're absolutely right !
I had in mind to put the Paho client tests in the same
project that the client itself (still in a Maven approach),
something like:
org.eclipse.paho.client.mqttv3
├── src
│ ├── main
│ │ └── java
<-- main sources
│ └── test
│ └── java
<-- Tests are here
Let's wait for Ian's point of view.
On Thu, Jun 14, 2012 at 12:07 AM, andypiperuk@xxxxxxxxx
<andypiperuk@xxxxxxxxx>
wrote:
Guys,
there's likely to be overlap here with stuff that Ian
Craggs was hoping to be adding to the project, so it may
be worth holding off until he can work out what that
contribution might look like - in the interests of
avoiding too much duplication.
Also needs consideration in terms of where in the
repository "tree" protocol-compliance test suites would
sit.
On Wed, Jun 13, 2012 at 12:42
PM, Nicolas DEVERGE <ndeverge@xxxxxxxx>
wrote:
Thanks,
I'll take a look at it !
On Wed, Jun 13, 2012 at
1:17 PM, Roger Light <roger@xxxxxxxxxx>
wrote:
Hi Nicolas,
> I'd be interested to port the client
side tests to the Java Paho client.
> Where should I start ?
You will find the tests in the test/lib
directory of the mosquitto
repository. You would need to create a
directory paho-java for
example, then duplicate all of the clients
to perform what is required
for the tests - publish a retained qos0
message with the correct
topic/payload and that sort of thing. The
existing code for the C, C++
and Python mosquitto clients should give you
what is needed.
There aren't that many client side tests
yet, it would be good to get
more so feel free to mention anything else
that needs testing.
_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/paho-dev
--
Andy Piper | Farnborough, Hampshire (UK)
blog: http://andypiper.co.uk
| skype: andypiperuk
twitter: @andypiper | images: http://www.flickr.com/photos/andypiper
_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/paho-dev
_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/paho-dev
|
