Thank you :) I was a bit nervous about doing that in this tutorial because I didn't want to turn anyone off, but it's how I structure my tests and I find it really valuable.

Thanks Chris! Glad you're enjoying the videos. Feel free to jump on the Discord server if you have any questions.

Thank you so much! That's really kind of you.

That's really kind of you, even if it is a little odd :)

Yeah, going to build a UI next to show how to use the access & refresh tokens.

now a curious to see

Glad it helped!

because the service function that we are mocking are async and they return a Promise, and in jest we are saying that it will return a Product. So typescript is saying , that the return type is not the correct one.

Why would you want to test the endpoint? You could mock the controller and asset that it was called with the expected request and response objects.

@@TomDoesTech The endpoint has the logic inside, it's not split with controllers, so the logic is declared on the POST request (e.g signing up a user with jwt middleware) and returning a token. Its all inside the routes folder.

@@arberi99 Do it exactly the same as I did it in the video. Tests should care about implementation, all they should care about is that given X input, Y should happen or Y should be returned, how your function does that shouldn't have anything to do with the test. Having said that, split your code up a bit and it will make your life easier. Check the video before this one to see how I did it: kzfaq.info/get/bejne/eL2FnJlzuJ-4ZY0.html

It's an autocomplete plugin for zsh

I think it's just the default theme

@@TomDoesTech okay thank you!

Yes, supertest is for sending HTTP requests in your tests

If your problem is that it can't get the value when you're running the tests, it's because you haven't called dotenv.config() before running the tests. You should be able to add it to a script that runs before your tests run. Otherwise, just generate some public and private keys that you use for tests and put them in test.ts

@@TomDoesTech oh yeah, that was my problem, the dotenv.config() call, I used that on a file that call the one I was testing, but not on the actual file. Thanks

Just mock it like it's a function, because that's what it is

@@TomDoesTech Ok, thank you very much

Di you watch the part where I refactored the app?

Hey Mohamed, thank you for your kind comments. The video you're after is here: kzfaq.info/get/bejne/pbmqZZahtajUdo0.html Then you may want to add Google OAuth: kzfaq.info/get/bejne/h9pjfq2Ll9G1m2Q.html

Nope

I had the same issue, not sure if it is refactored somewhere in the 1st video, but repo shows "return res.send(user);" in the controller as well

Try importing supertest like `import * as supertest from 'supertest'`

​@@TomDoesTech It worked thank you!

Read the docs if the explanation wasn't clear enough. Supertest will start an instance of your application and run requests against it. Axios will just send a request to a given URL.

Nice video btw! Wrote my first nodejs (ts) tests!

You could argue for both, they test across multiple units of code, but I'd they say are unit tests. Don't get too wrapped up in what a test is called, be more concerned with how it makes your software more reliable.

@@TomDoesTech thats what I’m thinking as well, but for my assignment I need to get the correct definition. If I describe it like that I think it will be sufficient enough. Thanks for the vid 👍

@@TomDoesTech While I do find this a confusing subject when it comes to end points and especially databases, it's to my understanding that if one were to mock the database or API in any fashion that means disconnecting the reliance on another component to be functioning properly in order for a test to pass, it's a unit test. The reverse being an integration test when the code tests multiple aspects of the program at the same time; i.e. we write a test that connects to express which in turn runs a function that connects to a database and creates or modifies or deletes a user for example. The only confusion I have there is when we also consider end-to-end or end point testing which more or less involves connecting to say a page route, but does not involve connection to a database or other component? I find this especially confusing when using a template engine like .ejs where even a basic rout to get a page might also be required to render dynamic data. I suppose I could just write the tests to ignore the dynamic data aspect, focusing only on reaching status 200 or 302 for rerouting. On a different note, I found in my current project that jest loved to assume the server was open even when it should be closing since I separated my server listen from the app just like you did here with server.js - importing the server separately. let serverListen // teardown beforeEach(() => { serverListen = require("../server.js"); }); afterEach(() => { serverListen.close(); }); I found this little bit of code resolved the warning. I was running quite a few tests concurrently and solved those by changing serverListen = require("../server.js") to a specific port for each test file serverListen = app.listen("5006"). This was NOT always necessary, I just found it solved issues where one of my test suites would "butt heads" with another on and off. Great video overall. Good mocking content is actually tough to find in Javascript and since I am new, there's an amazon aws-sdk mocking issue driving me nuts atm hahaha. (I REALLY need to learn typescript and c#) >_

anoying issue

Bro, no you have to instal ts-jest as a dependency: for example: yarn add ts-jest -D

I don't see record about mongodb-memory-server in file 'package'. How I have to install it, globally or another way?

That's weird. Sometimes YT does weird stuff with comments.

@@TomDoesTech apparently it just deleted my response to this

@@NathanielBabalola We should show KZfaq how to build a website that works!

@@TomDoesTech hahaha, we actually should.

Testing against a database is a nightmare to manage in CI pipelines. If you think it's not testing enough, then test against a database. I'm usually pretty happy with the test coverage doing it this way.