8000 [Feature] Include local build and testing steps for contributors · Issue #6298 · ScoopInstaller/Scoop · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[Feature] Include local build and testing steps for contributors #6298

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

Open
SierraKomodo opened this issue Mar 1, 2025 · 4 comments
Open

Comments

@SierraKomodo
Copy link

Feature Request

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

While looking into fixing a bug report I posted, I had difficulties with figuring out how to build scoop from source (If that's even a powershell thing - I couldn't find any help from google on this either), or how to get the tests to cooperate and function while being run locally from a cloned repo.

This meant I can't properly test that any scoop CLI commands function properly after changes, nor can I run tests locally to ensure everything would still pass.

Describe the solution you'd like

A basic guide or list of steps on:

  • How to build or setup your local copy so you can run and test scoop commands. Bonus points if this can be done in a way that allows visual studio code's debugger tools to stop on breakpoints and step through the code.
  • How to set up and properly run the tests locally.

Describe alternatives you've considered

N/A

@niheaven
Copy link
Member
niheaven commented Mar 3, 2025

Just run ./bin/test.ps1, it will run all the test for Scoop Core (though some functions may not contain test scripts).

If you add or modify some scripts, make sure that you add proper tests under tests folder.

@SierraKomodo
Copy link
Author

Just run ./bin/test.ps1, it will run all the test for Scoop Core (though some functions may not contain test scripts).

That's the process I was following, and was unable to get a state that was passing despite the code passing in github actions on this repo. Here's the output when run on the current state of /develop:

Image

stdout.log

@niheaven
Copy link
Member
niheaven commented Mar 4, 2025

It's okay in my local machine, PS5 and PS7.

Image

Image

@SierraKomodo
Copy link
Author

It's okay in my local machine, PS5 and PS7.

Image

Image

I'm guessing there's some dependency or additional first-time step I'm missing. Any ideas from the logs I posted?

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

No branches or pull requests

2 participants
0