quasarframework / quasarframework/quasar-testing

Setup CI for test-projects

Open
#239 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

dogfood
Dominant language
TypeScript
Stars
184
Forks
67
Avg merge
20h 53m
Merged PRs (30d)
5

Description

Replaces https://github.com/quasarframework/quasar-testing/issues/2

We should setup CI for tests available into test projects, such as we're able to test AEs features via AEs themselves

We should at least cover Cypress ones since we already know how to setup them thanks to Milos, and we can link those to another project into Cypress Dashboard
Jest/Vitest tests should be simpler to setup than Cypress ones, but Jest AE doesn't seem to work with Vite right now


If possible, we should also run these tests when there's a release for app-webpack and app-vite minor (or patch?) version.
In these cases we should run only tests into the relevant test project: into test-project-vite if a new app-vite version is released and same for webpack. test-project-app won't have any new updates so it's not considered into this feature

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 with .github/workflows/tests-on-pr.yml and inspect the test-project-vite, test-project-app, and webpack test-project setup. Use the existing Cypress workflow as the reference, then determine how Cypress and the simpler Jest/Vitest tests should run and how app-vite or app-webpack releases should trigger only their relevant project tests. Done means the test projects run in CI and the requested release coverage is defined.

Written by the indexing model from the issue text.

Assessment

Tech stack
cypress, github-actions, typescript, vite, webpack
Domain
ci-cd, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.