Don't use wasm-pack in CI (#2648)

* don't use wasm-pack for wasm tests

* use proper version of wasm-bindgen-cli

* also run with chrome driver

* use cargo pkgid
This commit is contained in:
Muhammad Hamza 2022-04-29 17:50:34 +05:00 committed by GitHub
parent c4338a7e05
commit 653aa542b3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 30 additions and 8 deletions

View File

@ -125,22 +125,44 @@ jobs:
override: true
profile: minimal
- uses: jetli/wasm-pack-action@v0.3.0
with:
version: "latest"
- uses: browser-actions/setup-geckodriver@latest
- uses: nanasess/setup-chromedriver@v1
- uses: Swatinem/rust-cache@v1
- name: Install wasm-bindgen-cli
shell: bash
run: |
if [ ! -f "Cargo.lock" ]; then
cargo fetch
fi
VERSION=`cargo pkgid --frozen wasm-bindgen | cut -d ":" -f 3`
cargo install --version $VERSION wasm-bindgen-cli
- name: debug
run: |
geckodriver --version
echo ""
which geckodriver
chromedriver --version
echo ""
which chromedriver
echo ""
wasm-bindgen --version
echo ""
which wasm-bindgen
- name: Run tests - yew
run: |
cd packages/yew
wasm-pack test --chrome --firefox --headless -- --features "wasm_test"
CHROMEDRIVER=$(which chromedriver) cargo test --features wasm_test --target wasm32-unknown-unknown
GECKODRIVER=$(which geckodriver) cargo test --features wasm_test --target wasm32-unknown-unknown
- name: Run tests - yew-router
run: |
cd packages/yew-router
wasm-pack test --chrome --firefox --headless
CHROMEDRIVER=$(which chromedriver) cargo test --target wasm32-unknown-unknown
GECKODRIVER=$(which geckodriver) cargo test --target wasm32-unknown-unknown
unit_tests:
name: Unit Tests on ${{ matrix.toolchain }}

View File

@ -39,9 +39,9 @@ members = [
"examples/suspense",
# Tools
"tools/changelog",
"tools/process-benchmark-results",
"tools/benchmark-struct",
"tools/benchmark-hooks",
"tools/changelog",
"tools/process-benchmark-results",
"tools/website-test",
]