Unit and Integration testing COMPARED

Подписаться 53 тыс.

Просмотров 19 тыс.

50% 1

Unit testing vs integration testing? There is a lot we need to tell you.
▶ Contact Jelvix: jelvix.com
▶ For RU-vid partnerships: youtube@jelvix.com
Subscribe for more tech tips and tutorials: / @jelvix
▶ LINKS:
- Best QA Methodologies - jelvix.com/blog/qa-testing-me...
▶ Time codes:
00:00 What is unit testing?
00:46 What is integration Testing?
01:21 Benefits of unit testing
02:07 Benefits of integration testing
02:31 Unit vs integration testing
04:33 Contact Jelvix
▶ Follow us:
Facebook - / jelvixcompany
Twitter - / jelvix
Instagram - / jelvix
Linkedin - / jelvix
Upwork - www.upwork.com/ag/jelvix/
▶ About this video:
Unit testing is concentrated on one part of the entire app in total isolation. Usually, it’s a single class or function. Ideally, the unit does not have any side effects. Ok, it’s clear - you develop a new feature and you test this feature. Nice.
But here comes Integration testing. It takes all the modules of software and tests them as a group to make sure they work well together.
---
Disclaimer:
The content in this video is based on company's experience. The primary purpose of this video is to educate and inform. Note that Jelvix is not responsible for the results of advices that were taken without considering individual situation and goals of your business. Jelvix strongly recommends to perform your own independent research before making any critical decisions. If you have a complaint about something or find your content is being used incorrectly, please contact Jelvix.
This video is available for private, non-commercial use only. You may not edit or modify this video.

Наука

Опубликовано:

19 июл 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 17

@Jelvix Год назад

Are you ready to implement both of tests in your workflow? Waiting for your comments!

@monicasmith6007 Год назад

Great video explained the difference between unit and integration tests. Thx

@Jelvix Год назад

Thank you for reaching out and providing us with valuable feedback.🔥

@kenadams5371 Год назад

Thanks for the explanation. I would like to see in your next videos something about UI testing as well.

@Jelvix Год назад

We'll figure something out, stay tuned.

@kenadams5371 Год назад

@@Jelvix I'm expecting more videos))

@williamjones2128 Год назад

Simple and clear explanation!

@Jelvix Год назад

We’re so happy to hear from you! Thank you for your valuable feedback. 💗

@petergarcies4640 Год назад

So cool. I am learning a lot from your channel 😎

@Jelvix Год назад

We appreciate you sending us your feedback. 😉

@ChanceMinus Год назад

Thank you.

@manuelfaner7167 Год назад

thank you!

@Jelvix Год назад

Glad you liked it!

@jessicabrown5723 Год назад

🤔Is integration testing done by developers or testers?

@Jelvix Год назад

It's highly individual. It all depends on the company and the project requirements 🤗

@jessicabrown5723 Год назад

@@Jelvix Thanks for the quick answer!

@grokitall 26 дней назад

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.