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

Improve testability #130

Closed
mads-hartmann opened this issue Nov 21, 2022 · 0 comments · Fixed by #135
Closed

Improve testability #130

mads-hartmann opened this issue Nov 21, 2022 · 0 comments · Fixed by #135
Assignees

Comments

@mads-hartmann
Copy link
Contributor

We'd like to establish a pattern that we like for writing tests for Leeway.

Leeway is heavily dependent on having a filesystem to operate on. We were thinking of including a small abstraction for specifying Leeway projects (workspace, components, packages, scripts) in Go code which we could then use to generate proper Leeway workspaces in a temporary folder. We could then run leeway there, and write assertions against the Go model.

It would be nice to do this at the same time as #122 so that we can be a bit test-driven in that refactor of Leeway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

2 participants