Integration tests #8487
Comments
farmaazon
added
d-intermediate
|
ideally the PM would remove any temporary directories after it's done as well |
farmaazon
added
the
s-research-needed
farmaazon
removed
the
s-research-needed
|
Updated the description, loosening somewhat the requirements: as we expect to remove rust build script soon, the new command is optional. Also, after a brief research I discovered https://playwright.dev/docs/api/class-electron - as playwright for electron testing just gets the path to executable, we should test the actually build package (without running PM ourselves)
|
|
Adam Obuchowicz reports a new STANDUP for yesterday (2024-09-25): Progress: Managed to run integration test on electron package. Worked on "sandboxing" the test environment (so the user's local projects won't be cluttered), discussed how to manage login. It should be finished by 2024-09-30. Next Day: Next day I will be working on the same task. Test on every environment |
|
Adam Obuchowicz reports a new STANDUP for yesterday (2024-09-26): Progress: Tested integration tests on various platforms (with Ilya's help on macOS). Last cleanups and created a PR. Also added fixes to previous PR with autosized input: the enter key wasn't handled properly. It should be finished by 2024-09-30. Next Day: Next day I will be working on the same task. Check how to easily enable integration tests in CI. |
A stub for integration tests to be run locally; part of #8487 To run tests, you need to: 1. Build IDE package: `./run ide build` 2. set ENSO_TEST_USER and ENSO_TEST_USER_PASSWORD to some working credentials (I used my personal account, but there will be also test user soon) 3. run `corepack pnpm -r --filter enso exec playwright test` The tests are run with a separate projects directory set up in tmpdir, so any local workspace dir is not affected. The only test so far just checks if it's possible to log in and create a new project.
|
Adam Obuchowicz reports a new STANDUP for yesterday (2024-09-30): Progress: The last issues of CI integration tests: the missing xvfb on linux, and some error (probably to small timeout?) on macOS. It should be finished by 2024-10-02. |
Added a step for packaging IDE which runs integration tests. This is an additional step, not a job, because here I'm sure the package will exist and won't be built unnecessarily twice. Technically I could make a job downloading it from GH action, but didn't want to invest time to rust scripts. Once Bazel will be fully introduced, the integration test will be improved. # Important Notes Fixes #8487
github-project-automation
bot
moved this from 👁️ Code review
to 🟢 Accepted
in Issues Board
|
Adam Obuchowicz reports a new STANDUP for the provided date (2024-10-01): Progress: Working on integration tests It should be finished by 2024-10-02. Next Day: Next day I will be working on the same task. Finish working on integration tests |
|
Adam Obuchowicz reports a new STANDUP for the provided date (2024-10-02): Progress: Fixed all issues on CI with integration tests. Created a PR and got an accept. It should be finished by 2024-10-02. Next Day: Next day I will be working on the #10668 task. Start working with E-Hern on unifying dashboard and gui projects. |
Automatic tests of GUI with the real backend connection. They could be playwright tests which assume there is a running project manager instance.
OPTIONAL, as it would be replaced with Bazel scripts soon: The build script should have working command
./run integration-testswhich spawns PM and run those tests. The Project Manager should be configured in such a way, that it creates projects in temporary directory (to not clutter user project list) - the old integration tests had a similar mechanism.If the above will be nontrivial (or in case of lack of time), having pnpm script for running tests (assuming there is an already built electron package) is enough for this task.
As output of this task, there should be one test scenario of "typical new project flow" where we create new project, add some nodes there, browse visualizations, collapse node, enter it, check visualizations there and leave it.
The text was updated successfully, but these errors were encountered: