**Software Testing Tutorial #19 - What is White Box Testing - Notes** **Comparing with Black Box Testing:** - Recap of black box testing where only inputs and outputs are focused. - White box testing focuses on internal logic and code understanding. **White Box Testing Explained:** - Also known as clear box testing, structural testing, or glass box testing. - Analogy of an open "box" that exposes internal mechanisms and code. - Unlike black box testing, white box testing comprehends system's implementation. **Analogy with Calculator:** - In black box, interact with calculator for output, no knowledge of internals. - In white box, open calculator's "box," analyze internal code. - Craft test cases to evaluate logic and structure of calculator's code. **Testing Techniques in White Box Testing:** 1. **Statement Coverage**: Ensure each code statement is executed at least once. 2. **Branch Coverage**: Guarantee every branch or decision point is taken. 3. **Condition Coverage**: Focus on code conditions and test all outcomes. 4. **Loop Testing**: Verify behavior within loops and iterated sections. 5. **Path Testing**: Examine different execution paths and test each one. **Application of White Box Testing:** - Often done during unit testing and integration testing. - Developers write unit tests to validate implemented logic. - Ensures seamless integration and collective functionality in integration testing. **Advantages and Conclusion:** - White box testing allows scrutiny of system's internals and logic. - Validates implementation quality, identifies potential bugs. - Ensures reliable and robust system performance. - It's an essential part of software testing to ensure comprehensive quality.
@jankrizek59132 жыл бұрын
Few weaks ago i starded "SW tester" course according ISTQB and your courses give me the advice in my study, many thanks, John
@geekcode1036 Жыл бұрын
kzbin.info/www/bejne/h4m1oJ6DhKd8qpY&feature=share Pls do subscribe for more testing career related stuff
@azamtariq25593 жыл бұрын
very good presentation sir. plz do some focus on mic quality. thank you
@dalicortez91962 жыл бұрын
Thank you so much for making videos like this accessible to all, this is awesome.
@softwaretestingmentor2 жыл бұрын
Most welcome. Keep watching for more videos!
@marynapokotylo2 жыл бұрын
thank you so much for sharing your knowledge.
@hameedsk444 Жыл бұрын
Sir different names of white box testing unit, cler, glass, transperent,code, structural, open right or rong
@sirborkington10527 ай бұрын
Thank you mate, very clear and helpful
@softwaretestingmentor7 ай бұрын
Glad it helped Keep watching and sharing.
@shraddhaathani73532 жыл бұрын
Excellent sir 🙏understood very well
@softwaretestingmentor2 жыл бұрын
Thank you so much.😊 Keep watching for more videos!
@comedyman1123 жыл бұрын
is white box testing reserved only for automated testers?
@VickieEB3 жыл бұрын
Very Detailed. Thank you
@softwaretestingmentor3 жыл бұрын
Thank you Victoria. I am glad it’s helpful!
@mandalavijay1720 Жыл бұрын
Good teaching
@supportmodi_yogi6063 жыл бұрын
Well explained sir
@jeyhunaliyev17653 жыл бұрын
going to subscribe really liked your content 👍🏻✅
@softwaretestingmentor3 жыл бұрын
Thanks and you're welcome.
@gyanbaimishra94662 жыл бұрын
Thank you sir
@softwaretestingmentor Жыл бұрын
You are so welcome! Keep watching for more videos and tutorials.
@xiamojq6213 жыл бұрын
Understood sir
@jagmeetsingh72593 жыл бұрын
👌👌👌👌 excellent , found helpful
@elnino612 жыл бұрын
Thanks a lot
@AbrarMehmood-y5v Жыл бұрын
I don't have bachelor degree in IT or any other related but if I understand the testing than Can I get software testing job
@viveksinghbhadauriya79298 ай бұрын
Absolutely Yes
@khetankhobragade712 жыл бұрын
Sir please make a interview vedios on manual , Api , database and Unix testing , I like the ways you explains
@HoD999x Жыл бұрын
i think whitebox testing is a really bad idea. 1. you lock the implementation. i can no longer change (improve) the code without also having to change the test 2. the test is *way* more complex, meaning it now needs tests itself (because if i can trust complex code right away i need no tests in the first place) 3. the test itself is harder to read because it's not clear which variable has which value for which reason