Tech timeout 20 hours or greater

[patrickhlauke]

This branch never had a pull request made. Suggest we either take/consider this, or delete both this PR and branch.

[netlify]

✅ Deploy Preview for wcag2 ready!

Name	Link
🔨 Latest commit	6de837a
🔍 Latest deploy log	https://app.netlify.com/sites/wcag2/deploys/67127a8ad0a6920009499ac9
😎 Deploy Preview	https://deploy-preview-4058--wcag2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[bruce-usab]

Discussed on TF call 9/13. This would be new technique from a stale branch. TBD.

[bruce-usab]

@goodwitch are you still of the opinion that this is an important gap to fill? That is, do we need a technique for testing that a timeout does not occur within 20 hours? And if so, is what @patrickhlauke has drafted sufficient? Thank you.

[patrickhlauke]

And if so, is what @patrickhlauke has drafted sufficient?

to clarify, this is literally just taking the branch that @goodwitch opened at the time and turning it into a PR. it will need massaging to be mergeable

[bruce-usab]

On TF call 10/4, @alastc offered to ask @goodwitch offline about the need for this PR.

[patrickhlauke]

I would suggest closing this (and deleting the branch), as we likely don't need a technique that literally says "to test there's a 20 hour timeout, set yourself a timer for 19 hours 59 minutes and check if anything happens in that last minute..."

[mbgower]

Discussed on today's TF call. Attempts were made to contact creator. Closing as unnecessary.