Are you ready to implement both of tests in your workflow? Waiting for your comments!
@williamjones21282 жыл бұрын
Simple and clear explanation!
@Jelvix Жыл бұрын
We’re so happy to hear from you! Thank you for your valuable feedback. 💗
@kenadams53712 жыл бұрын
Thanks for the explanation. I would like to see in your next videos something about UI testing as well.
@Jelvix2 жыл бұрын
We'll figure something out, stay tuned.
@kenadams53712 жыл бұрын
@@Jelvix I'm expecting more videos))
@petergarcies46402 жыл бұрын
So cool. I am learning a lot from your channel 😎
@Jelvix Жыл бұрын
We appreciate you sending us your feedback. 😉
@monicasmith60072 жыл бұрын
Great video explained the difference between unit and integration tests. Thx
@Jelvix Жыл бұрын
Thank you for reaching out and providing us with valuable feedback.🔥
@jessicabrown57232 жыл бұрын
🤔Is integration testing done by developers or testers?
@Jelvix2 жыл бұрын
It's highly individual. It all depends on the company and the project requirements 🤗
@jessicabrown57232 жыл бұрын
@@Jelvix Thanks for the quick answer!
@grokitall2 ай бұрын
due to the conflation of integration testing with end to end testing in the video, the answer is not quite as simple to answer as it should be. when doing continuous integration, unit tests are done first, and integration tests only cover those aspects you cannot unit test. together they act as regression tests against the stable public api of the code and are designed to determine if the code does what the developer intended. they are designed to be extremely fast, on the order of a few minutes for the entire suite of tests, to give feedback between committing the code, and pushing it upstream prior to the next piece of coding. once this is complete, you pass on towards a continuous delivery pipeline. in this stage, you do things which act as acceptance tests, which check that what the developer built matches what the customer actually wants and needs. this step is designed to show that the product is fit to release. the aim is that you give it enough resources to finish in about an hour. most end to end and user interface tests fit here, along with performance tests. unit tests are best done by the developer, preferably before the code is written. integration tests can be written by either the developer, or by someone else, but both are run as a continuous integration test on the development machine prior to pushing the code upstream. acceptance tests are usually generated when the customer is present, and are often created by someone else, but can be done by the developer if he is the one dealing with the customer. i hope this clarifies it a bit.