## Description 1. Added a parameter --maxWorkers=50% to run tests. Is the [official recommendation](https://jestjs.io/docs/cli#--maxworkersnumstring) for running tests in CI. This allows you to run tests in CI about **60 seconds** faster. 2. Deleted mocha package because we use jest to run test. For history: I tried to use [@swc/jest](https://swc.rs/docs/usage/jest) to speed up the tests, but it didn't show any improvements since we have a lot of long tests(see pict) that need to be improved point-by-point. Also, this approach does not work with imports of the type import * as _ from ""; [read more here](https://github.com/swc-project/swc/issues/5205) See code example [here](https://github.com/appsmithorg/appsmith/pull/23797/files). <img width="703" alt="Снимок экрана 2023-05-29 в 10 36 27" src="https://github.com/appsmithorg/appsmith/assets/11555074/37a2a065-124b-4c16-a5ec-e7868dc2dc13"> #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing > #### How Has This Been Tested? > Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration. > Delete anything that is not relevant - [x] Manual - [x] Jest - [ ] Cypress ## Checklist: #### Dev activity - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Test-plan-implementation#speedbreaker-features-to-consider-for-every-change) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans/_edit#areas-of-interest) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed --------- Co-authored-by: Valera Melnikov <melnikov.vv@greendatasoft.ru> |
||
|---|---|---|
| .. | ||
| client | ||
| server | ||
| util | ||