michleza
commented
1 year ago - Avoid using numbered bullet points for requests that are not a set of steps.
- Put the command line tool workflow into the advanced tools section
- image files don't display. check to see if a full URL is required or if you can still use a relative path to the file
- In workflows like use groupings and annotations I don't think it's necessary to provide an exhaustive list of menu options to test. You could probably shorten it by putting a couple of the menu options into parenthesis after the request like so: Perform actions from group edit menu by right clicking on a group in Script Canvas graph window (cut, paste, collapse, etc...)
- Workflows with steps like generate translation data may need a couple steps describing how to perform those requests. It should probably also mention that the action has a noticeable delay when you perform the step since you can easily confuse it with being unresponsive or nonfunctional.
- Make sure steps aren't missing or implied from the more complicated workflows. The input handler workflow says to press spacebar to print but the previous steps don't tell the user how to generate that file and configure the fields to use spacebar.
- Update the timeboxes to reflect all the new work requests.
The following commit uploads an updated version of script-canvas-tests.md which broadens the scope of testing with new areas and workflows.
Together with it are: /scripts/OldGraphTest.scriptcanvas /scripts/ontick.scriptcanvas
/images/SCaudio_script.png /images/SCcreate_input_bindings_file.png /images/SCinput_handle_script.png /images/SCnodes_dimming_hover_over.png /images/SCnode_delete_particles.png /images/SCnode_nudging.png
Which are needed by the new workflows and areas.
Signed-off-by: Mateusz Szweda 86953456+LB-MateuszSzweda@users.noreply.github.com