You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: