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

comments on QUICK_START phase 2 #65

Closed
jpiesing opened this issue Feb 16, 2024 · 2 comments
Closed

comments on QUICK_START phase 2 #65

jpiesing opened this issue Feb 16, 2024 · 2 comments
Assignees
Labels
Blocker documentation Improvements or additions to documentation

Comments

@jpiesing
Copy link
Contributor

Some comments on QUICK_START phase 2 in no particular order. These come from trying it for the first time in a while.

  1. The copy/paste box is unhelpful because it includes a lot of text that has to be deleted.
    I suggest splitting it into two boxes each of which contains only a URL and nothing more with "or" and "if you have provided valid certificates" being moved outside the copy/paste box.

  2. "select the tests to be executed on DUT from provided lists" is true but unhelpful for a QUICK_START.
    I suggest adding something like this (perhaps with a screen capture)

A good place to start for first time users would be to deselect all test groups by using the "None" button and then select one simple test, e.g. by expanding either cfhd_12.5_25_50-local or cfhd_15_30_60-local and then selecting just the sequential track playback test with stream t1 as shown.
image

  1. I'm uncomfortable that it focuses on using the mobile phone as the UI to configure and start the session. I always use the PC on which I installed the test runner. Please consider adding both options. The device under test and the PC with the test runner may be on a corporate network not reachable from the public internet. Many companies may not allow personal mobile phones to be connected to the corporate network and may not provide testers with company mobile phones that are so allowed. These people won't be able to use a mobile phone.

More comments may be added.

@jpiesing jpiesing added documentation Improvements or additions to documentation Blocker labels Feb 16, 2024
@FritzHeiden
Copy link
Collaborator

Merged #68 which should fix this

@jpiesing
Copy link
Contributor Author

Pull request accepted.

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

No branches or pull requests

2 participants