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
I think that it might make sense to create integration tests for the command line interface, using a known input state (i.e. local package repository, known paket.template setup) and comparing it to a known output state.
See, for example, the EndToEnd tests of the Official NuGet client (this is a GitHub mirror of the Codeplex repository), which use a test framework written in PowerShell, and could serve as an orientation.
The text was updated successfully, but these errors were encountered:
Following some bugs with the command line interface, namely:
packet pack
and multiple paket.template files #893 (Issues withpaket pack
)paket find-packages
not working in1.16.0
)paket find-package-versions
sorts the output in the wrong order)I think that it might make sense to create integration tests for the command line interface, using a known input state (i.e. local package repository, known paket.template setup) and comparing it to a known output state.
See, for example, the
EndToEnd
tests of the Official NuGet client (this is a GitHub mirror of the Codeplex repository), which use a test framework written in PowerShell, and could serve as an orientation.The text was updated successfully, but these errors were encountered: