sfdx-lwc-jest icon indicating copy to clipboard operation
sfdx-lwc-jest copied to clipboard

Run Jest against LWC components in SFDX workspace environment

Results 39 sfdx-lwc-jest issues
Sort by recently updated
recently updated
newest added

Currently `@salesforce/sfdx-lwc-jest` has an explicit dependency on these [core LWC packages](https://github.com/salesforce/lwc): - `@lwc/compiler` - `@lwc/engine-dom` - `@lwc/engine-server` - `@lwc/module-resolver` - `@lwc/synthetic-shadow` - `@lwc/wire-service` And these [lwc-test](https://github.com/salesforce/lwc-test) packages: - `@lwc/jest-preset` -...

enhancement

### Description First of all, my apologies if the issue description lacks enough details or it is not thorough enough as it is the first issue I report via Github....

bug

### Description connectedCallback method does not complete calls to mock modules before tests start. #### Steps to Reproduce customComponent.js ```js import {api, LightningElement} from "lwc"; import getResult01 from "@salesforce/apex/Controller01.getResult01"; import...

bug

### Description When sfdx-lwc-jest is installed globally, tests run with mocked Apex Method are failing #### Steps to Reproduce From the root of a SFDX Project with LWC tests using...

Bumps the lwc group with 6 updates in the / directory: | Package | From | To | | --- | --- | --- | | [@lwc/compiler](https://github.com/salesforce/lwc/tree/HEAD/packages/@lwc/compiler) | `6.7.2` |...

dependencies

Bumps the theoretically-non-breaking group with 5 updates: | Package | From | To | | --- | --- | --- | | [@babel/core](https://github.com/babel/babel/tree/HEAD/packages/babel-core) | `7.24.6` | `7.24.7` | | [@babel/eslint-parser](https://github.com/babel/babel/tree/HEAD/eslint/babel-eslint-parser)...

dependencies

### Description When running unit tests using the new `lightning/toast' module, I get an error. ```bash Cannot find module 'lightning/toast' from 'path/to/lightningComponent/js' ``` #### Steps to Reproduce ```js // JS...

This would be the first step to achieving #349. We should not have multiple `@lwc/*` package dependencies, but rather a top-level `lwc` dependency, and do our imports like this: ```js...

enhancement

I am reopening an issue for the continuation of #350 -- I added a note for Nowlan Lawson on that but it looks like he moved on... The suggested workaround...

Bumps the theoretically-non-breaking group with 9 updates in the / directory: | Package | From | To | | --- | --- | --- | | [@lwc/compiler](https://github.com/salesforce/lwc/tree/HEAD/packages/@lwc/compiler) | `8.16.4` |...

dependencies
javascript