It is hard to add features to Telepresence without causing a combinatorial explosion of testing

telepresenceio / telepresence

Local development against a remote Kubernetes or OpenShift cluster

https://www.telepresence.io

Other

6.56k stars 515 forks source link

It is hard to add features to Telepresence without causing a combinatorial explosion of testing #628

Closed plombardi89 closed 3 years ago

plombardi89 commented 6 years ago

We want to add features to Telepresence without causing a combinatorial explosion of testing in the Telepresence project. We will measure our success by the ability to add copy-deployment, method=none, and tests for the mount argument.

ark3 commented 6 years ago

Stages that need to be tested include:

intent (argument parsing, etc.)
setup (inspecting local and cluster state, other stuff)
proxy (e.g., swap-deployment) #657
connection (set up port forward, ssh tunnel)
environment
filesystem
outbound (e.g., vpn-tcp)
launch
wait
cleanup

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. Issue Reporter: Is this still a problem? If not, please close this issue. Developers: Do you need more information? Is this a duplicate? What's the next step?

donnyyung commented 3 years ago

I believe this is no longer an issue in Telepresence 2. Here are the docs on how to install Telepresence (https://www.telepresence.io/docs/latest/install/), please re-open if you still see this issue in our latest version!