Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use virtual environment for functional tests rather than production atsigns #211

Open
cpswan opened this issue May 2, 2024 · 0 comments · May be fixed by #476
Open

Use virtual environment for functional tests rather than production atsigns #211

cpswan opened this issue May 2, 2024 · 0 comments · May be fixed by #476
Assignees
Labels
enhancement New feature or request

Comments

@cpswan
Copy link
Member

cpswan commented May 2, 2024

Is your feature request related to a problem? Please describe.

The functional tests introduced in #210 make use of a couple of atSigns, which is an approach we've used elsewhere (e.g. at_python) and that isn't always robust.

Describe the solution you'd like

Spin up a virtual environment in the test runner and use that instead (as we do for at_client_sdk and at_server)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
2 participants