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

Feature request: screenshots #121

Open
kmturley opened this issue Jan 13, 2024 · 0 comments
Open

Feature request: screenshots #121

kmturley opened this issue Jan 13, 2024 · 0 comments

Comments

@kmturley
Copy link
Contributor

kmturley commented Jan 13, 2024

Use-cases to support screenshots

1) Debugging visual issues

When testing a plugin, you need to test functionality and also visual, layout and accessibility. Being able to take screenshots during the testing process allow developers to check that the build on that platform (Linux, Mac, Windows) "looks" correct.

Currently pluginval can load a plugin in the GUI and perform automated actions/tests. When there is an issue a log is outputted. This is similar to other test automation frameworks such as Selenium or Jest. However other test frameworks commonly support screenshots to debug visual issues. Visual issues are important to fix and prevent.

2) Automate plugin preview images

Plugin sites require some plugin preview images to display to users before they download and install plugins. Currently screenshots are made manually by developers for every release.

If pluginval supported screenshots, developers could run pluginval in their CI pipeline to test and also auto-generate the preview image of that build for a release e.g.

  • Linux-v2.1.0.png
  • Mac-v2.1.0.png
  • Windows-v2.1.0.png

Thank-you!

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

1 participant