mirror of https://github.com/tauri-apps/tauri
f0d95a4244
* feat(testing) add test apps, docs for testing Signed-off-by: Daniel Thompson-Yvetot <denjell@quasar.dev> * feat(testing) add test apps, docs for testing, fix entry and generator Signed-off-by: Daniel Thompson-Yvetot <denjell@quasar.dev> * feat(tauri) use require.resolve Signed-off-by: Daniel Thompson-Yvetot <denjell@quasar.dev> * feat(rust) fix for cargo sources Signed-off-by: Daniel Thompson-Yvetot <denjell@quasar.dev> * chore(version) bump Signed-off-by: Daniel Thompson-Yvetot <denjell@quasar.dev> * feat(tauri) setup tauri object Signed-off-by: Daniel Thompson-Yvetot <denjell@quasar.dev> * feat(demo) setup tauri object Signed-off-by: Daniel Thompson-Yvetot <denjell@quasar.dev> * feat(entry) fix generator Signed-off-by: Daniel Thompson-Yvetot <denjell@quasar.dev> * feat(docs) prepare quasar spa docs Signed-off-by: Daniel Thompson-Yvetot <denjell@quasar.dev> |
||
|---|---|---|
| .. | ||
| cloudish | ||
| trollbridge | ||
| README.md | ||
README.md
TESTING
While we get the test harnesses unified, which will happen before the 1.0.0 stable release, we are using the manual testing approach of building real Quasar apps and vetting them for functionality.
In this folder there are two of them, distinguished by the fact that one uses a localhost server (cloudish) and the other is a pure rust host (trollbridge). These follow the principles laid out in the Design Patterns.
PRE-RELEASE NOTE
Until upstream quasarframework/quasar is merged and released as v1.1.0, we are linking against a local git clone.
Here is how to do that (assuming you are in the base of this repo):
$ yarn
$ git clone https://github.com/lucasfernog/quasar.git # premerge usage of our working fork
$ cd quasar
$ git checkout feature/tauri-package # premerge usage of our working fork
$ cd app && yarn
$ cd ../ui
$ yarn && yarn build
$ cd ../../test/cloudish
$ yarn add @quasar/app@link:../../../quasar/app ../../quasar/ui # or yarn install if a previous version of yarn
$ quasar dev -m tauri