It's needed to write the test for plan QE to verify that WTO advisory works as expected.

An approximate plan that should be clarifications in the issue scope:

1. Check installing
   1. register catalog sources ('make register_catalogsource' from https://github.com/redhat-developer/web-terminal-operator/tree/v1.0.x);
   2. install Web Terminal Operator;
2. Check that it's not possible to use custom creator label
   1. just after installing operator -

      oc apply -f https://raw.githubusercontent.com/devfile/devworkspace-operator/master/samples/web-terminal.yaml
      

      ^ note: if that command failed because of permissions leak - do again until devworkspace is not created

   2. make sure that it's marked as failed once operator is installed.

      oc get devworkspaces.workspace.devfile.io web-terminal -o=yaml
      

   3. remove created devworkspace instance

      oc delete devworkspaces.workspace.devfile.io web-terminal
      

3. Check terminal to kubeadmin
   1. terminal button appear on OpenShift Console for kube:admin but it's not possible to open terminal because of error message``;
   2. remove created DevWorkspace instance to clean up resources
4. Check terminal for developer
   1. terminal button appears on OpenShift Console for developer;
   2. terminal is created and started successfully;
   3. terminal is opened when it already exists;
   4. kubeconfig is initialized ( oc whoami);
   5. oc/kubectl/helm/kn/tkn/odo completion works as expected;
   6. terminal is not idled after idle timeout (15 minutes is the default value) if there is any activity in the terminal frame;
   7. non-owner is not able to exec into workspace-related pod, e.g.:

       > oc exec -n dev-ws workspacec52e42993cb64cb9-69bc7c8fd8-j5msm -c dev echo hello
      Error from server (The only workspace creator has exec access): admission webhook "validate-exec.devworkspace-controller.svc" denied the request: The only workspace creator has exec access
      

   8. terminal is idled after timeout (15 minutes is the default value) if there is no activity in the terminal frame;
   9. open terminal again and make sure that existing stopped workspace is successfully started;
5. Check uninstallation procedure
   1. uninstallation procedure described in operator description works as expected and Terminal button disappear, workspace-related pod is removed, webhooks are removed and it's possible to exec into another pod;