Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document how to run the tests #321

Closed
kevinburke opened this issue Jun 17, 2019 · 4 comments
Closed

Document how to run the tests #321

kevinburke opened this issue Jun 17, 2019 · 4 comments

Comments

@kevinburke
Copy link

It would be nice if the fvt/start_IMA.sh script that is apparently necessary to run the tests was referenced anywhere else in the documentation.

Alternatively, it would be nice if the test suite could work out of the box for people who don't have access to an IBM device - maybe we could skip the tests that require an IBM machine if it's not present.

@alsm
Copy link
Contributor

alsm commented Jul 3, 2019

By default all that is required for the tests to run is an mqtt broker at 127.0.0.1:1883, there are no tests that require an IBM system.

@kevinburke
Copy link
Author

I guess as someone who is trying to get the tests running but unfamiliar with this project you might want to document what sort of broker needs to be running there, then.

You might also want to update the documentation in fvt/README.md. I don't know what FVT is but I tried running the tests, saw that stuff broke and then started reading and saw this.

The FVT tests are currenly only supported by IBM MessageSight.

Support for mosquitto and IBM Really Small Message Broker might be added in the future.

@MattBrittan
Copy link
Contributor

Pull request #366 (merged a week ago) included updates to fvt/README.md (there was some info re mosquitto at the bottom of the file but it conflicted with what was said at the top) and added a fvt/docker folder which should hopefully be of assistance to anyone trying to find an easy way to run the tests.

@MattBrittan
Copy link
Contributor

Closing this issue as I believe the updates in #366 have sufficiently improved the documentation re tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants