Repository navigation
Address follow-up workshop review feedback - #2
Conversation
|
Tested on the real device ✅ |
|
|
||
| Before continuing, launch the app and confirm that it still shows the Step 5 | ||
| screen: the navigation tile row and the horizontal movie list must both be | ||
| visible. If you have already completed Step 7, restore the Step 5 screen before |
There was a problem hiding this comment.
I would remove the line about having completed step 7 - if someone jumps ahead thats on them
| If the list is empty, connect a physical Vega device before continuing. See [Step 1: Run on a Fire TV Stick](./step-01-setup-and-run.md#run-on-a-fire-tv-stick) if you need to configure the device. | ||
|
|
||
| UI Fluidity testing requires Appium `2.2.2` and the Vega `kepler` Appium driver `3.30.0`. KPI Visualizer also lists `@amazon-devices/kepler-performance-api` as a prerequisite. | ||
| Copy the physical device serial from the first column and use it throughout the |
There was a problem hiding this comment.
Can you please do a pass through to make sure the language is the same as the other sections?
|
|
||
| ## 6.3 Choose how to run the measurement | ||
| ```bash | ||
| vega exec perf generate-test-template \ |
There was a problem hiding this comment.
Is there a reason we are going for a custom test?
There was a problem hiding this comment.
When I run the default UI Fluidity test it does not enter this app’s movie list. The custom scenario focuses Movies, enters the list and performs the horizontal scrolling for both FlatList and Carousel.
|
Updated with the default test after your changes to the movie list, can you merge so the workshop can be tested from 0 to 7? |
| If the list is empty, connect a physical Vega device before continuing. See [Step 1: Run on a Fire TV Stick](./step-01-setup-and-run.md#run-on-a-fire-tv-stick) if you need to configure the device. | ||
|
|
||
| UI Fluidity testing requires Appium `2.2.2` and the Vega `kepler` Appium driver `3.30.0`. KPI Visualizer also lists `@amazon-devices/kepler-performance-api` as a prerequisite. | ||
| Copy the physical device serial from the first column and use it throughout the |
There was a problem hiding this comment.
What do you mean by first column?
|
|
||
| Do not assume that the Carousel will always produce a particular number. Device state, images, background activity, and the exact focus path can affect the result. The useful outcome is learning how to make a repeatable comparison. | ||
|
|
||
| If you want to investigate a failing result after the workshop, Amazon's [Investigate UI Fluidity Issues](https://developer.amazon.com/docs/vega/0.24/investigate-ui-fluidity.html) guide explains CPU profiling and trace analysis. |
There was a problem hiding this comment.
Can you add example results?
| 4. Play/Pause works. | ||
| 5. Back or Exit returns to the movie row. | ||
|
|
||
| Manual testing with the Virtual Device remote is enough for this step. Appium |
anishamalde
left a comment
There was a problem hiding this comment.
Approving but please address the small comments
Summary
Validation
git diff --checkstreaming-tv-prompt.txtis the only prompt remaining