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

Basic testing of Puter in CI #377

Open
AtkinsSJ opened this issue May 6, 2024 · 0 comments
Open

Basic testing of Puter in CI #377

AtkinsSJ opened this issue May 6, 2024 · 0 comments
Labels
idea An idea for a feature/improvement

Comments

@AtkinsSJ
Copy link
Collaborator

AtkinsSJ commented May 6, 2024

It would be helpful to have automated testing that Puter can build and run correctly. This can help prevent issues appearing in setups that the dev team don't use. (eg, Windows and Docker.)

The general process would be something like:

  1. Get a copy of the repo
  2. npm ci, and check for errors
  3. npm start, and check for errors
  4. Access the hosted Puter website
    • This could start out as a simple curl call to check the response code, but ideally we'd run some basic tests using something like selenium-webdriver to interact with the page.
  5. End the puter process

Ideally there would also be a variation of this that creates a Docker container from the repo and runs that - we get some issues when running in Docker that don't occur otherwise.

At a basic level, this would ensure that Puter at least can be installed and run, on whichever OSes we configure the CI task for. If we want to get fancy though, we could test that individual parts of the UI, like signing up, logging in, and creating files all work as expected, and across different web browsers.

@AtkinsSJ AtkinsSJ added the idea An idea for a feature/improvement label May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
idea An idea for a feature/improvement
Projects
None yet
Development

No branches or pull requests

1 participant