Replies: 4 comments 1 reply
-
Did you ever figure it out? |
Beta Was this translation helpful? Give feedback.
0 replies
-
i would like to know this as well |
Beta Was this translation helpful? Give feedback.
0 replies
-
Bump |
Beta Was this translation helpful? Give feedback.
1 reply
-
bloop... |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I've read the testing docs, but i continue struggling to e2e test my Tauri app.
After reading the docs i've understood that i can use automations like Selenium or Webdriver IO to run my tests, but the provided example is too simple, it does not even touch the Tauri API usage, i know that i can mock this component, but if i want to really e2e test my application the ideal scenery will be if it run like a real Tauri app (the WebView and Rust backend with the IPC doing the bridge between the two).
I've searched a lot but don't found any examples on doing this, do you have any examples or ideas on how to get this done?
If it's not possible then i will have to test my Rust backend Commands and my JS frontend parts separately, doing unit-tests like in each end of my Tauri app?
This is the app that i'm currently working on:

A example of test that i might want to do is: when i click in the select file button, the system file picker opens to select the file and after the selection, the selected file path is shown in the disabled input that lays at the left of select file button. But if i mock this file picking action (that is being handled by Tauri
dialog
API), how can i grant that my application is really working?Beta Was this translation helpful? Give feedback.
All reactions