tauri-apps / tauri-apps/tauri-docs

[request] e2e webdriver selenium examples

Open
#2,430 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
MDX
Stars
1.1k
Forks
887
Avg merge
2d 8h
Merged PRs (30d)
48

Description

Question you want answered

How do I test Tauri with selenium?

Where did you look for an answer?

As requested I post my question from Discord here ^^

Page URL

No response

Additional context

I created a generic Selenium library for Tauri (it is probably bloated as it's my first JavaScript code where I learned how to build a proper library and documentation). The documentation is available at https://bukowa.github.io/tauri-e2e/index.html, and I am using it successfully in my project. However, I don't think it would be a good addition to the Tauri v2 examples for how to perform end-to-end (E2E) testing.

As you can see here: https://github.com/bukowa/tauri-e2e/tree/master/selenium/javascript/src/selenium, implementing Selenium classes for WebKitGTK2 and WebView2 is quite simple, and it is possible to use them with the native Selenium API: https://bukowa.github.io/tauri-e2e/documents/3__Selenium_API.html.
(The old documentation for V1 regarding Selenium was not working, which caused many issues.)

Is there any way that Tauri docs can benefit from some of this? I personally struggled a bit and have seen many issues about E2E testing problems. Currently, I am wondering if there are better ways to test the app than Selenium, perhaps using something more native to test everything and not just the webview part?

Are there any tracking issues or someone with more knowledge about how better and proper cross-platform testing can be performed?

Are you willing to work on this yourself?
  • I want to work on this myself

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the Tauri v2 examples and the existing V1 Selenium documentation, then compare them with the linked tauri-e2e Selenium API and its WebKitGTK2 and WebView2 implementations. Determine whether the docs should cover Selenium or another cross-platform E2E approach; done means the testing guidance and example scope are agreed and documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
documentation, testing
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.