5 Types of Testing Software Every Developer Needs to Know!
HTML-код
- Опубликовано: 12 июн 2024
- Software testing is a critical part of programming, and it is important that you understand these 5 types of testing that are used in software development. In this video, I go over the importance of the software testing pyramid and explain how the testing changes at each level. I also touch on MC/DC code coverage, which is critical if you every want to work in defence or aviation.
☕️ I don’t accept paid sponsorships and I have turned off mid-video ads. You’re welcome! If you would like to support my channel see: ko-fi.com/alexhyett
📨 Join my free weekly newsletter for advice, technology and more: newsletter.alexhyett.com
If you want to learn a bit more about how to test your software, then Zero To Mastery have a great course on testing that is worth checking out: academy.zerotomastery.io/a/af...
🗺️ Backend Developer Roadmap: www.alexhyett.com/backend-dev...
📝 Related blog post: alexhyett.com/types-of-testing/
🎓 RECOMMENDED COURSES (Use code FRIENDS10 for 10% off)
The Complete Web Developer Course - academy.zerotomastery.io/a/af...
The Complete Junior to Senior Web Developer Roadmap - academy.zerotomastery.io/a/af...
Complete SQL + Databases Bootcamp - academy.zerotomastery.io/a/af...
📚 RECOMMENDED BOOKS
Clean Code - geni.us/5AEwj2
Clean Architecture - geni.us/yBrTX
Domain Driven Design - geni.us/WiR0Q0x
Design Patterns - geni.us/5ncUt
Developer Hegemony - geni.us/lAXy
Pragmatic Programmer - geni.us/GfNj9
Data Structures and Algorithms Made Easy - geni.us/sqg6kJ
Refactoring - geni.us/ufAP0mE
The Productive Programmer - geni.us/IT9WiN
Pragmatic Thinking and Learning - geni.us/x81A
Test Driven Development - geni.us/HFV52
Microservices - geni.us/8vMA
🚀 MY FAVOURITE TOOLS
PIA VPN - piavpn.com/AlexHyett (83% off + 4 extra months free!)
Visual Studio Code - code.visualstudio.com/
Obsidian - obsidian.md/
Notion - affiliate.notion.so/alexhyett
⏳ TIMESTAMPS
00:00 Introduction
00:09 Software Testing Pyramid
00:25 Unit Tests
00:54 Code Coverage
01:05 Modified Condition Decision Coverage
01:34 Component Tests
02:22 Integration Tests
03:12 White Box and Black Box Testing
03:50 End-to-End Tests
05:32 Manual Testing
You can check out more of my favourite tools on my website:
www.alexhyett.com/tech/
🔗 MY KEY LINKS
🌍 Blog - www.alexhyett.com/
🐘 Mastodon - social.alexhyett.com/@alex
🧑💻WHO AM I
I’m Alex, a Software Developer and RUclips working in the UK. I make videos about software development to help developers with the skills they need to be senior developers. As well as this RUclips Channel, I also write articles on my website (alexhyett.com) as well as write a regular newsletter that contains some thoughts to help aspiring developers.
‼️ DISCLAIMERS
Some of the links in this description are affiliate links, for which I get a small commission, at no extra cost to you 🙂. I appreciate you supporting my channel so I can continue providing you with free software development content!
#coding #programming #developer 
Наука
Better than any video I've seen on the Internet on this topic. Useful for both client and testers. Great Work!
Great straight to the point video! Thank you!
Thank you!! So helpful!
Thanks Alex, concise and straight to the point explanation. 👌
You're welcome, I hope it was useful for you.
This video was very useful, thank you very much! Your editing is amazing :)
Thank you! I am glad it was useful.
Hi! Thanks for this video! It's incredibly helpful, especially for those who are just beginning their journey. It's great that you are sharing your knowledges. Our QA team also created good video for QA and future QA - we collected the software testing trends for 2024
thanks great explanation!!
Got the concept in 6 mins vs 3hr of lectures and mediocre bragging thank you 🙏
Good explanation❤️
Thank you, I am glad you liked it.
Alex thank you for your video, it was very useful. Could you please give an example of a component testing for example on Facebook login page’s.
excellent explanation...just one doubt...what is the exact difference between component
and integration testing then?
So component testing is testing a component in isolation from everything else. So think of an API but with any external API calls and the database mocked out.
Integration testing is testing multiple components together.
thanks a lot
You’re welcome!
Good stuff!
Thanks! I am glad you enjoyed.
Great!
Great video, I have just one question. What are API tests ? They seem to me like they are actually component tests, but these naming conventions can be quite confusing.
API testing, a subset of component testing, focuses on evaluating the functionality, reliability, performance, and security of application programming interfaces (APIs) to ensure seamless communication between different software components and systems. Basically in Component or Integration testing, you use the program API to do your test.
what about regression test?
Awesome
thanks ,Alex , but can't understand the component test .
think if you're testing a car. You would want to test the engine on its own (component testing). The individual parts of the engine will also need to be tested i.e fuel injectors (unit testing). Then you want to test how the engine fits into the car model (integration testing)
Interestingly, you mention unit testing and component testing as different levels of the pyramid, but regarding the ISTQB Foundation Level Syllabus:
v 4.0: 'Component testing (also known as unit testing) focuses on testing components in isolation'
v 3.1.1: 'Component testing (also known as unit or module testing) focuses on components that are separately testable.'
Great video anyway! :)
jUST ONE QUESTION ARE THESE THE LEVELS OF TESTING OR TYPES OF TESTING
i think levels
Every Lions fan knows MC DC stands for Motor City Dan Campbell
Your MCDC explanation is incorrect, you would need 4 for this senario. you need to show how each variable affects the outcome.
The coverage you explained is predicate coverage, which is higher subsumption than MCDC.
Why are we still teaching a model that is 15 years old? None of our software architectures follow the same patterns as what was popular in 2009. Many of the struggles that we saw in 2009 that puts UI and E2E tests at the top of the pyramid no longer exist.
They still do, it depends on your industry. In embedded SE things move slower, tests are more difficult, and a significant amount of testing could be physical 😅
too fast ! and not good accent