Branch Branch Revolution

Happy Thanksgiving. (US) Puttering on here for fun in between cooking.

How do I see the result of the AI flowchart request? I saw it the first time I clicked on the link but now I don’t know where to find it. I see the code that might make it but not the result.

I think we might need two sets of testing documents one for regular users and one for the people doing the work on the code. I don’t know what would make the code side easier or better, mostly I can think from the user end. I think a Flowchart with check points might be useful.

I am playing with a spreadsheet here not sure it is a good design It does help me understand more about what should be happening at each point. We need tools for users to understand what the machine is doing and how to report and troubleshoot:

Link I’ll keep working on it:Maslow Testing Rubric - Google Sheets
Static CSV file of current state:

Maslow Testing Rubric - Sheet1(1).csv (3.8 KB)

Screenshot:

As an attempt to make a rigorous testing state chart? Not sure it is useful. Only advantage to it is if one filled it out one could pull data as 1 or 0 or something similar from the testing report. I do like it from a noob user side as a way to understand what the machine is doing.

What state does the machine go to after retract all?

What state does it go to if you release tension? Can you apply tension and keep going?

wouldchuck wrote:

What state does the machine go to after retract all?

retracted

What state does it go to if you release tension?

Extendedout

Can you apply tension and keep going?

yes.

David Lang

1 Like

wouldchuck wrote:

How do I see the result of the AI flowchart request? I saw it the first time I clicked on the link but now I don¢t know where to find it. I see the code that might make it but not the result.

in github, the .md files can be viewed (go to files changed, then in the menu to
the right at the top of the diff for the file select ‘view file’

that should take you to a link like:

I think the other file formats are only available by checking out the code and
running the build script

I think we might need two sets of testing documents one for regular users and
one for the people doing the work on the code. I don¢t know what would make
the code side easier or better, mostly I can think from the user end. I think
a Flowchart with check points might be useful.

A flowchart of what? I think the state flowchart is more for developers than
anything else.

a flowchart of what to do for users would be good.

for that the blockdiag or graphwiz dot format is going to be the best way to do
things.

David Lang

1 Like