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

test: add end-to-end testing setup #99

Closed
wants to merge 1 commit into from
Closed

test: add end-to-end testing setup #99

wants to merge 1 commit into from

Conversation

gsaslis
Copy link
Collaborator

@gsaslis gsaslis commented Dec 14, 2023

Fixes #35

@gsaslis gsaslis requested a review from maninak December 14, 2023 07:32
@gsaslis gsaslis marked this pull request as draft December 14, 2023 08:59
@gsaslis gsaslis changed the title Add end-to-end tests Test: Add end-to-end testing setup Dec 14, 2023
@gsaslis gsaslis changed the title Test: Add end-to-end testing setup test: add end-to-end testing setup Dec 14, 2023
@gsaslis gsaslis force-pushed the feat/e2e_tests branch 15 times, most recently from d5fe226 to 9120904 Compare August 8, 2024 23:26
includes a new GH Actions workflow that has the necessary
preparatory steps for e2e testing:

- install radicle-node and radicle-httpd
- create profile
- create test repo

following instructions from
https://code.visualstudio.com/api/working-with-extensions/testing-extension

Note: we are using the custom test runner, because this allows us to open VS Code
with the radicle repo we have previously created in the e2e tests

Signed-off-by: Yorgos Saslis <yorgo@protonmail.com>
@gsaslis gsaslis marked this pull request as ready for review August 8, 2024 23:31
@gsaslis
Copy link
Collaborator Author

gsaslis commented Aug 8, 2024

ok @maninak this is now in a good place.

I'll leave the one failing lint check to you.

The endToEnd tests:

  • install radicle
  • create a new radicle profile
  • create a new radicle repo
  • open that radicle repo with VS Code

at that point, you can write your tests to start verifying whatever scenarios you feel are the most important. I'd recommend just starting with 1 scenario.

For example that could be, listing the patches and opening a patch (that you have previously created in the radicle-init step), and verifying you can view the patch.

As you will also see in the commit message, I have followed the guide in: https://code.visualstudio.com/api/working-with-extensions/testing-extension#the-test-runner-script .

If it helps, I'm happy to go over these changes together as well once you're back.

🖖🏼

@maninak
Copy link
Collaborator

maninak commented Nov 18, 2024

Closing in favor of #158

@maninak maninak closed this Nov 18, 2024
@maninak maninak deleted the feat/e2e_tests branch November 18, 2024 07:34
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

Successfully merging this pull request may close these issues.

End-to-end testing pipeline
2 participants