The tests based on our CHE project: https://github.com/eclipse/che should reflect nexn test plan:

• If Web Terminal Operator is installed, "web terminal" button appears in top right after a refresh
• Clicking the "web terminal" button in the UI gives you a terminal
• If you're a cluster admin, you don't get to pick a namespace
• These flows (+ UI-based configuration) I believe are covered by OCP tests, so not something we necessarily need to verify beyond "I can get a terminal"
• Once started, terminal is logged in as the current OpenShift user (oc whoami)
• Then there are secondary, specific functionality tests; these can be verified either via UI or (more easily, likely) via API calls that don't include the UI:
• Typing help in a web terminal prints basic help message
  wtoctl binary is present in image
• Idle timeout works – to test, exec wtoctl set timeout 30s , wait for new pod, and verify that DevWorkspace is stopped after ~30s of runtime, with stopped-by: inactivity annotation
  *(optional) verify that wtoctl commands do what we expect them to; IMO this should be tested at an earlier stage (e.g. unit tests, on my TODO list)