spec.ts | Write tests for your types | Assertion library

I've gotten Jest debugging up and running many times. For some reason in this repo (that I'm new to) the debugger will stop in jest.js:

but won't stop in the test itself. The test:

I'm running into a problem on my unit tests after upgrading Swiper 6 to 7. I'm using Angular 12 and Swiper 7.3.1. Before upgrading it the unit tests were working fine (Swiper version 6.5.9).

I'm using the SwiperModule in my tests like this:

I have just created a spec file under that path is integration>mweb>account>address-mweb.spec.ts. Cypress UI sees my all spec files but while running it cannot establish a connection with tests.

How can I fix this, any idea?

p.s there is no network issue.

Waiting to connect on terminal

Cypress UI appearance

We have a NestJS project with several modules. Suddenly, some tests stopped working with errors all like

FAIL libs/backend/nest/pipes/src/lib/iso-date-validation.pipe.spec.ts

● Test suite failed to run

ENOENT: no such file or directory, open D:\git\my-nest-project\libs\backend\nest\pipes\src\lib\iso-date-validation.pipe.spec.ts'

It knows what test to run, but then it claims it can't find the test file. Sometimes we get a couple of these errors, sometimes dozens.

These errors are happening randomly (not always on the same tests) locally on my machine as well as on our Jenkins server and on other developer environments as well. I can reproduce this on Windows/Mac/Linux.

There were no changes to the test or project configuration files that would have triggered this change. In fact, I have checked out previous versions of the codebase that built reliably in Jenkins and now they have the same random test errors.

I have tested on clean nodejs environments with nothing installed globally except npm.

Using the jest --verbose flag gives me no further details.

The jest config in a NestJS project is multi-layered, so it's hard to display the whole thing here, but I don't understand how this could be a configuration issue because the tests used to run fine and the configuration files have not changed.

I have tried clearing the jest cache, but the results are not consistent. On some occasions I can get a clean test run after clearing the cache.

More often than not, the test failures occur in a module that has some React .tsx templates, but not always. Sometimes a pure Typescript module will fail.

I recently updated one of my Angular projects to Angular 13. After the updates I got some weird errors when trying to run the unit tests in the project.

I created a minimal example inside a fresh Angular project to reproduce this behavior:

I'm trying to use jest/testing library to make a test in my nextJS application and when I put a component inside the render method, it complains, is my first time using jest/react test in next, I follow the documentation but it still do not work:

the error:

I migrated the project from version 25 to 27 and the module '@ngrx/effects/testing' cannot more found. In my case the baseUrl in the project set to './src'.In other projects with baseUrl '.' and with the same jest, angular, ngrx the tests run without problems. Maybe some additional configuration for jest required?

This the message I get:

Cannot find module '@ngrx/store/testing' from 'src/app/app.component.spec.ts'.

some dependencies from package.json:

Most examples I've seen of how to test a Prisma-injected NestJS Service (e.g. prisma-sample in testing-nestjs) are for "end to end" testing. They actually access the database, performing actual queries and then rolling back the results if necessary.

For my current needs, I want to implement lower-level "integration" testing.

As part of this, I want to remove Prisma from the equation. I want the focus to be on my service's functionality instead of the state of data within the database and Prisma's ability to return it.

One big win of this approach is that it obviates the need to craft "setup" queries and "teardown"/reset operations for specific tests. Instead, I'd like to simply manually specify what we would expect Prisma to return.

In an environment consisting of NestJS, Prisma, and Jest, how should I accomplish this?

UPDATE: The author of the testing-nestjs project pointed out in the comments that the project does have an example of database mocking. It looks nice! Others may still be interested in checking out the Gist that I've linked to as it includes some other useful functionality.

I'm trying to add a MatBottomSheet to an app that I'm building in Angular 13. I'm trying to follow the example here:

https://material.angular.io/components/bottom-sheet/examples

However, I constantly fail and get this error in the browser:

core.mjs:6495 ERROR NullInjectorError: R3InjectorError(AppModule)[MatBottomSheet -> MatBottomSheet -> MatBottomSheet]: NullInjectorError: No provider for MatBottomSheet! at NullInjector.get (core.mjs:11139) at R3Injector.get (core.mjs:11306) at R3Injector.get (core.mjs:11306) at R3Injector.get (core.mjs:11306) at NgModuleRef.get (core.mjs:22189) at Object.get (core.mjs:21862) at lookupTokenUsingModuleInjector (core.mjs:3349) at getOrCreateInjectable (core.mjs:3461) at Module.ɵɵdirectiveInject (core.mjs:14720) at NodeInjectorFactory.FooterResultComponent_Factory [as factory] (footer-result.component.ts:10)

This is my app.module.ts where I think I have declared the required dependencies: