You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On three different applications Angular are failing all test that use @angular-devkit/schematics. Two of the applications were passing fine on Angular 17.2.0 but failed after upgrading to 17.3.7. The third application was a new one that was created on 17.3.7 to just for testing purses.
Standard jest tests, eg testing 'Hello world' are passing. But anything using schematics is throwing with the error The encoded data was not valid for encoding utf-8.
Minimal Reproduction
Create a new Angular application on 17.3.7 (latest version). Change to using Jest. Create a unit test that uses any schematics, and it throws with an encoding utf-8 error.
Expected Behavior
Expect test to be able to run against anything with schematics, not to straight away fail.
I wonder if that's an issue with the builder or jest-preset-angular.
Could you try to reproduce it with clean jest-preset-angular setup (without the @angular-builders) in order to confirm it is indeed an issue with the builder?
Regardless, a minimal reproduction repository would speed up the investigation.
Describe the Bug
On three different applications Angular are failing all test that use @angular-devkit/schematics. Two of the applications were passing fine on Angular 17.2.0 but failed after upgrading to 17.3.7. The third application was a new one that was created on 17.3.7 to just for testing purses.
Standard jest tests, eg testing 'Hello world' are passing. But anything using schematics is throwing with the error The encoded data was not valid for encoding utf-8.
Minimal Reproduction
Create a new Angular application on 17.3.7 (latest version). Change to using Jest. Create a unit test that uses any schematics, and it throws with an encoding utf-8 error.
Expected Behavior
Expect test to be able to run against anything with schematics, not to straight away fail.
Environment
Test file example:
The text was updated successfully, but these errors were encountered: