automate combinations

[hchiam]

critical first steps:

• critical first question: can it run after refreshing page or after submitting? if it can't then it can't really test submitting with different combinations - might have to resort to Chrome's built in recorder or Puppeteer?
  • ANSWER: yes, as long as there's some variable that persists that you can read on load.
• can the popup trigger code to run on the page?

easier:

• 1) try combinations of inputs that are visible and become visible --> WIP: append to list of (can-be-)visible inputs (and retain that logic that checks visibility before setting value) --> just get all inputs, and only edit the currently visible ones
• 2) to determine possible values, detect input type
• 3) track visible inputs --> WIP: append to list of (can-be-)visible inputs (and retain that logic that checks visibility before setting value) --> just get all inputs, and only edit the currently visible ones
• 4) don't refresh memory of showable inputs when running automation --> storage variable --> just get all inputs, and only edit the currently visible ones
• 5) think about feasibility of submitting after each combo in quick succession - WIP: consider adjusting the automation approach, maybe add a selector or choice of action? window.history.back();? need to actually submit in certain situations, so:
  • give option but warn user
  • increment the string value used for email/name to avoid false negatives because of duplicates.
• (At this point I can deploy to Chrome at https://chrome.google.com/webstore/devconsole and https://chrome.google.com/webstore/detail/form-utility-belt/hpeggcbpjddkihbnjpbjfllbmecelkbc) before continuing with the harder stuff below

harder:

• 6) any more TODO comments
  • handle continuing combos() automation where left off before auto-refresh page after each submit
  • reset form upon next combo if submitting? https://www.w3schools.com/jsref/tryit.asp?filename=tryjsref_form_reset resetAllInputs() will need debugging to fix timing issue, which breaks running thru combos #43
  • handle stopping combos() automation if the user doesn't want to continue on refresh
  • input could pull allowed values from a <datalist> element too
• handle ambiguous possible values? #44
  • 7) for ambiguous possible values, check the text of the label of the input? (a short list) --> automatically handle inputs that may not have type set explicitly #66
  • 8) for ambiguous possible values, check for elements with their intersection boxes touching the input? --> automatically handle inputs that may not have type set explicitly #66
  • 9) for ambiguous possible values, as a last resort, maybe ask/let user to demonstrate values for inputs that are ambiguous? --> use input value set in the form as the only allowed value #55
  • 10) maybe ask user to demonstrate inputs that should become visible upon interaction, then try combinations of inputs that are visible and became visible from user interaction

[hchiam]

moved remaining tasks into new issues