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

Plans on migrating from @percy/agent to @percy/cli #8

Open
bgturner opened this issue Jul 11, 2022 · 4 comments
Open

Plans on migrating from @percy/agent to @percy/cli #8

bgturner opened this issue Jul 11, 2022 · 4 comments

Comments

@bgturner
Copy link

I notice that the @percy/agent project is no longer supported and they are urging users to migrate to @percy/cli:

This package has been deprecated
Author message:

@percy/agent is no longer supported. Please upgrade to @percy/cli https://docs.percy.io/docs/migrating-to-percy-cli

-- https://www.npmjs.com/package/@percy/agent

Are there any plans on upgrading laravel-visual-testing to use percy's new tooling?

@jszobody
Copy link
Member

I don't have much time to work on it myself, but I'd happily review a Pull Request if you or anyone else wanted to take a stab at this?

@bgturner
Copy link
Author

I'm new to the Laravel ecosystem, so I was hoping that you would be familiar enough with it for a quick fix! :)

I'll see if I can carve some time out to take a closer look!

@nathangross
Copy link

Following—would love to use this!

@royduin
Copy link

royduin commented Mar 13, 2024

Just use the CLI directly in your actions: https://www.browserstack.com/docs/percy/ci-cd/github-actions and take screenshots with Dusk: https://laravel.com/docs/master/dusk#taking-a-screenshot

- name: Percy snapshots
  run: npx percy upload tests/Browser/screenshots
  env:
    PERCY_TOKEN: ${{ secrets.PERCY_TOKEN }}

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

No branches or pull requests

4 participants