OK, found a solution.

Should use jest.useFakeTimers()

Note: Put the code above just after import section in your test file.

jest.useFakeTimers()

With above it's extremely important to understand this

jest.useFakeTimers() mocks out setTimeout and other timer functions with mock functions.

If running multiple tests inside of one file or describe block, jest.useFakeTimers(); can be called before each test manually or with a setup function such as beforeEach.

Not doing so will result in the internal usage counter not being reset.

I would like to contribute to the answer.

Well let's see the error message

ReferenceError: You are trying to 'import' a file after the Jest environment has been torn down.

Torn down means: Jest already finished running and some part of your code is trying to execute after jest torn down or exited your test. This is pretty common on Javascript due to its asynchronous nature.

Sometimes it happens after a promise callback getting executed for example:

import { someProcess} from 'a-library'

task.job().then(result => {
    someProcess(result)
})

In the example above the code imports someProcess from a-library

If the method job from the task object takes longer than the jest execution its callback (then() invocation) will run outside jest because jest has continued. Therefore when someProcess gets executed it will be loaded from a-library so jest will complain that you are trying to load a library after jest has been torn.

The answer marked as the solution is partially right because calling jest.useFakeTimers() will prevent your code to wait the n seconds you supposed to wait calling setTime or similars making your code artificially sincrhonoyus

Making your test await those method calls would help you understand better your code.

The code that worked for me was

describe("Some test set " , ()=>{

    let heavyWorkinService = library.workingService();

// We are marking the test function call as async

     test(("Name of the test"), async  ()=>{

// we are awaiting heavyWorkingService to done its job 
          await   hevyWorkingService("some data")
        })
})

In my real scenario my code was getting data from firebase, because am not using mocks for this test it was trying to import firebase after .get() data read returned so marking the test as async and calling the method with await keyword solved my problem

Of course there are a lot of ways to dealing with this error, just wanted you to know the true reason behind this error so you can work in the right solution for your tests!