Just a friendly suggestion, I recommend adding visuals to make it easier for us to follow along with what you're saying. Especially with QA stuff, it can get a bit dense to follow with words alone.
Great video! Thanks!I've learned so many things out of it. For entering the QA field with no previous work experience: what is the best own project that one can have on their CV? What this project should contain? I'd love to see your video about it. Take care!
Thank you for the feedback! The best project is a real one. Find a fried who owns a company, find a company that will agree to take you without pay, find a course that offers internship in a real startup so you could get used to processes in the company 👍
API testing could be everything that has input and output. We understand that the API of the REST service and some hardware socket APIs are based on different lvl and related to the OCI models. The author describes the usual web-based app with the REST backend under the hood. In 95% of cases, the unit tests are done by engineers and focused on covering methods of the code to be sure that the method and/or the smallest testable unit of an application are working properly. Technical, we can say that unit testing is also a kind of API testing because each method signature usually has its parameters and return type. Therefore, as I mentioned above, it's input and output, but mixing them is a bad idea. Moreover, if we are testing a part of your application locally, I would better call it module testing. Module testing aims to isolate a section of code and verify its correctness using stubs/mocks. It's just an additional view of the API and unit testing rather than the opposite view.
100% Agree 🙌🏼 API testing could be both: unit(if mocking data), integration, with server and DB. This is actually a good interview Q to see new the Engineer is
Thanks for the video. I was asked a question like when you do manual API testing you are using Swagger for validation but how about the automation part how do you do validation how can we answer that?
You can say that you validate data and schema with assertions. Each framework will have it's own assertion. So you can give an example based on the one you've used in your experience
Hi Liudmila, it is a part of the manual course. And we have api automation which is a part of test automation course. Are you interesting in taking manual api testing separately?
Just a friendly suggestion, I recommend adding visuals to make it easier for us to follow along with what you're saying. Especially with QA stuff, it can get a bit dense to follow with words alone.
Thanks for the heads up! Will do
Great video! Thanks!I've learned so many things out of it.
For entering the QA field with no previous work experience: what is the best own project that one can have on their CV? What this project should contain?
I'd love to see your video about it.
Take care!
Thank you for the feedback! The best project is a real one. Find a fried who owns a company, find a company that will agree to take you without pay, find a course that offers internship in a real startup so you could get used to processes in the company 👍
Dude ! Thank you very much. These are invaluable informations.
My greatest pleasure!
Thanks for your work! Well done!
Thanks for the video. Can you make short tutorials how to do unit and integration testing with mock?
Hi, Nuan, sure
API testing could be everything that has input and output.
We understand that the API of the REST service and some hardware socket APIs are based on different lvl and related to the OCI models.
The author describes the usual web-based app with the REST backend under the hood.
In 95% of cases, the unit tests are done by engineers and focused on covering methods of the code to be sure that the method and/or the smallest testable unit of an application are working properly.
Technical, we can say that unit testing is also a kind of API testing because each method signature usually has its parameters and return type. Therefore, as I mentioned above, it's input and output, but mixing them is a bad idea.
Moreover, if we are testing a part of your application locally, I would better call it module testing. Module testing aims to isolate a section of code and verify its correctness using stubs/mocks.
It's just an additional view of the API and unit testing rather than the opposite view.
100% Agree 🙌🏼
API testing could be both: unit(if mocking data), integration, with server and DB.
This is actually a good interview Q to see new the Engineer is
Thanks for the video. I was asked a question like when you do manual API testing you are using Swagger for validation but how about the automation part how do you do validation how can we answer that?
You can say that you validate data and schema with assertions. Each framework will have it's own assertion. So you can give an example based on the one you've used in your experience
Hey am I gonna learn api testing if I’m taking a automation course ?
We will teach you how to do api automation during test automation course. But you are required to already understand manual api testing.
Do you have an API testing course?
Hi Liudmila, it is a part of the manual course. And we have api automation which is a part of test automation course. Are you interesting in taking manual api testing separately?
@@CodemifyMmm, maybe both, maybe firstly manual API. IDK exactly