-
Notifications
You must be signed in to change notification settings - Fork 312
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
Write a test that prints out the default latency values for each device #201
Comments
Comment by @RossBencina TRAC migration: propagating ticket status from TRAC |
Comment by @williamspinelli Here is a little patch that I put together. For every device it prints a report like this
Could this be something acceptable? Or a different display format should be used? |
Comment by @RossBencina Thank you. The purpose of this test is to output data that we can combine into a survey of all host APIs. For this reason I think it would be best to have tabular output with one device per line. For the table format I think either CSV or Textile (assembla) table mark up. Textile tables are just | separated values instead of comma separated (see: http://redcloth.org/hobix.com/textile/quick.html#tables). It's not necessary to vertically align things, although of course that would be nice. My personal vote is for the Textile format, then we can paste the output straight into the Wiki. I think that you have the correct fields. I would like to see the columns in this order:
I hope that is OK, if you have a better idea, please shout out. |
Comment by @williamspinelli @rbencina So be Textile tabular format with vertically aligned columns =) |
Hi. I hope I can take this up and complete it. I have something working and will share an update soon. |
Created a PR with screenshot of the outputs - #844 |
Issue created by @RossBencina
Write a test that prints out host api and default latency values for each device. The output of this test need to be reviewed for each host API.
For each device print name, host API and the four default values:
This is needed as part of the process of resolving ticket #202, #97
The text was updated successfully, but these errors were encountered: