Very good video, I have been moved from an embedded developer to more of an white box testing role. We did the static checking and peer to peer reviews when some new functionality was to be delivered within the project, all with limited specifications if any. I have a lot of gaps in understanding with the concepts in testing and have been told to use a specific tool to perform this. Watching this video helped in understanding with concepts like "Statement coverage" or the differentiation of "Validation and Verification". I now look at the code I delivered in the past differently. I see I cannot have 100% Control flow for instance since I had a local static variable control an "if" statement so the test tool has no possible influence over that, there fore "branch coverage" could only be 50%, but the function has a state-machine with eight states that I could make test cases for at least. Anyway, I think a bit differently now....
We all will wast our time and invaluable efforts, Wall St tycoons and investment bank CEO can crash the global economy without technology and can avoid all possible testings, all they need is our superstition and faiths of their Jewish languages created policies and practices. Our psychology of trusts for authorities are all trashed by their simple hedge fund accounts.
All the problems were NOT testing problems but software and hardware development problems. Expecting testing to be the only people to be responsible for software quality is ridiculous. I wish people would STOP passing the buck to testing or allowing testing to take the blame is childish.
I have a telephone interview for a testing vacancy and this was a brill revision session! Thanks Philip
finally, a testing tutorial in a language/accent I can understand
Finally? English is the only language I know and it's not that big of a deal to me.
This is very methodically done. Awesome.
Very good video, I have been moved from an embedded developer to more of an white box testing role. We did the static checking and peer to peer reviews when some new functionality was to be delivered within the project, all with limited specifications if any. I have a lot of gaps in understanding with the concepts in testing and have been told to use a specific tool to perform this. Watching this video helped in understanding with concepts like "Statement coverage" or the differentiation of "Validation and Verification". I now look at the code I delivered in the past differently. I see I cannot have 100% Control flow for instance since I had a local static variable control an "if" statement so the test tool has no possible influence over that, there fore "branch coverage" could only be 50%, but the function has a state-machine with eight states that I could make test cases for at least. Anyway, I think a bit differently now....
This is a great video. Thank you Philip for sharing the same.
Very good video, with clear,perfect English speaking.
Very helpful and insightful video. Thank you Mr. Johnson.
I learned a lot form this video.
Thanks
Excellent video; thanks so much! :)
Thank you Sir!! Great video.
Thanks, I learned a lot.
Mahalo for posting this video.. Very helpful..
thank you !! very clear lesson!!!
thanku very much john ,its really clear and healpfull
Great
Well done Sir.
Hi, somebody know how to do integration testing of big-bang approach?
Thank you Sir
We all will wast our time and invaluable efforts, Wall St tycoons and investment bank CEO can crash the global economy without technology and can avoid all possible testings, all they need is our superstition and faiths of their Jewish languages created policies and practices. Our psychology of trusts for authorities are all trashed by their simple hedge fund accounts.
All the problems were NOT testing problems but software and hardware development problems. Expecting testing to be the only people to be responsible for software quality is ridiculous. I wish people would STOP passing the buck to testing or allowing testing to take the blame is childish.