Комментарии:
Excellent explanation. thanks so much
ОтветитьIntegration testing tests whether a software application works as intended when its different modules are integrated. The aim is to find bugs when the different modules interact with each other. Avo Automation helps enterprises run a series of test conditions against a fulfillment endpoint. It makes integration testing faster, error-free, and cost effective.
ОтветитьPerfect, man keep going
ОтветитьGreat
ОтветитьFinally something simple
ОтветитьSimple and clear expalnation 👌
ОтветитьFinally found a great video of integral testing
Ответитьgreat video! well done! thx
ОтветитьNice explanation, thanks.
ОтветитьThanks
ОтветитьMissed opportunity. The last sentence could have made a huge difference if you added for example "The choice of approach chosen depends on the system architecture and location of high risk modules. High risk models on low level will require top to down integration testing" or whatever the real case is. .
ОтветитьGreat explanation :)
ОтветитьIs integration testing a black box testing or white box testing? Is it done by developers or testers? please help me out.
ОтветитьHonestly i wish you were my professor! Very well explained and it such short time!
Thank you!
Good video, but I also expected to see how Driver and Stub classes must be written, too short explanation
ОтветитьThe clipart/Pictures and animations in the presentations are well coordinated.
very good job!
Excellent videos.. Thanks!
ОтветитьYou can not get better understanding of Testing anywhere else..
best videos ever.
well planned, organized, sequenced, and executed information..
the guy who is asked to do the dubbing job on the video speaks very clear as well.. knows how to articulate while uttering..
amazing...
excellent job done guys!
super..
Thanks a lot
very helpful!
Ответитьfor integration testing..who is gonna integrate those unit tested individual modules ? We will only do the testing of how modules react right ?
ОтветитьExcellent :) :) :)
ОтветитьVery helpful thank you
ОтветитьThis is not a integration testing, this is functional (end-to-end) testing. Integration testings tests just the border between two systems, but not the scenrio. For example integration testing tests CRUD for database tables and verifies that the data at lease will send or received, or mapping is correct, but who cares what user story do you implement? To test user stories you have to have all set of your systems and subsystems you will use.
So, testsers write articles for testers without knowledge what is integration testing.
Very imformative. Thanks Guru99
ОтветитьExcellent work!! Thank you so much :)
ОтветитьSuperb! explanation. thanks
ОтветитьThank you very much!
Ответитьor you can finish your project in 1 day by using only drivers and stubs
Ответить***** sir/mam can u please tell me which software or tools you used for creating this video . thanks
anuj
Great explanation! Tnx
ОтветитьThanks dat helped alot..!
Ответитьwow fantastic
Ответить