mine.js | :earth_asia: A Minecraft-like voxel engine built with JS/TS (formerly mcjs) | Runtime Evironment library

You may not be calling the function, it works. Can you try below code.

I did find the reason. It is indeed not an issue with the config flag but rather with my jasmine.json file.

What I thought the use of config flag was to specify the path to the file instead of the default spec/support/jasmine.json. It would then have the same behaviour as if the relative path to config was spec/support/jasmine.json.

But

F:\proj\dev-react-node-java>jasmine --config=src/server/spec/support/jasmine.json

is not the same as

F:\proj\dev-react-node-java\src\server>jasmine --config=spec/support/jasmine.json

What it does instead is like copying it to the path from where the command was called and then using it to run the tests.

Hence, what worked was changing the spec_dir field.

I can't pin-point the exact issue. It might have been due to use of blob: which was added to solve The issue was around content security policy issue. However, as pointed here (do I need to set content-security policy when running jasmine/karma test cases), if it was csp then the problem should happen all the time and not randomly

" What messages is the browser logging in the devtools console? If it’s failing because of CSP, then the browser would be logging specific error messages in the devtools console, explicitly saying what it’s blocking and why. So if you don’t see any messages in the devtools console, then you can safely rule out CSP as the cause of the failures you’re seeing. And if it were due to CSP, the failures wouldn’t be random; instead they’d be consistent. Also, adding a CSP policy to a document that doesn’t already have one isn’t going to fix anything; instead it can only cause further blocking to happen. " I did quite a few things to solve the issue 1) I changed jasmine.js to add a debug print which could give me some hint about what was going on.

You could do it like this:

Jasmine spyOn mocking function returns a Spy class object which does not represent any function call, but it has helper methods regarding mocking the function. You have to call expect directly to fs. in order to check if it's called:

fakeAsyncTest not support XHR, because it is not a time sensitive task, you need to use Mock Http such as Angular HttpTestController to test XHR. Or if you want to test the real XHR (which I think in the most case you should not), you need to use jasmine done.

Use the toHaveClass syntax of Jasmine.

Solved it. Once i moved the .spec files into the /src folder, Jasmine detected them without any problems.

If you're unit testing your home page you shouldn't be adding child components to your declarations. Instead you could just create a Stubbed version of that component. You can just put something like the below at the bottom of your spec file and add StubLeveltatusSidebarComponent to your declarations instead (you may need to stub out inputs as well).

@Component({ selector: 'app-level-status-sidebar', template: '' })

class StubLevelStatusSidebarComponent{}

Alternatively you can try adding the below to your configureTestingModule object and it should ignore missing children errors and continue on with the tests.

schemas: [NO_ERRORS_SCHEMA]