Integrate eSign Test with airSlate SignNow

Integrate esign test

Hello again, this is the second lecture of  the fourth week. What I wanted to do today   was to continue with graph based coverage  criteria, we saw how to test code based on   a graph coverage criteria. The basic idea  was to take the control flow graph model   it as a graph and then consider the  various structural coverage criteria   to be able to do graph coverage and then we  augmented the CFG with definitions and uses,   looked at du-pairs, du-paths and  tested it for data flow criteria. And what did we achieve by doing this? It  was basically white box testing of code,   we could cover the code see what statements were  executed, how many times loops were executed,   were loops skipped and so on, and  through examples we saw that it was   indeed useful to find the errors in codes. Now, I want to continue to use graph coverage   criteria, but instead of considering code  I want to be able to work with design,   graphs for design models. When it comes  to design the phase of testing that we   are looking at is what is called integration  testing. Integration testing basically assumes   that design puts the software into various modules  it puts together these modules and test set. So,   what I want to spend some time on with this  lecture is to help you understand the traditional   or the classical view of integration test. What is integration testing? How has it been   defined in the popular textbooks available on  software testing, how do graphs corresponding   to integration testing look like? So, today we  will look at the classical view of integration   testing any old book on software testing  that is existed for many decades will use   this view of integration testing. In the next  lecture what I will tell you is I will tell   you graph models for design and how to apply  structural and dataflow coverage criteria on   those graph models. We have to define slightly  new structural and dataflow coverage criteria   to be able to cater to graph models for  design we will do that in the next lecture.  This lecture we will just spend on  understanding integration testing   as it is always been classically presented  in several text books and software testing. So, when I say software design, what is it?  Software design for a large piece of software   is basically tells you details about how its  large piece of software is split into modules   since the software runs into several thousands  of lines, of code or even millions of lines of   code. It is all not going to be one flat piece of  code right; it is going to be split into several   components each component is going to be designed  and implemented by maybe by separate teams,   separate individuals and then they are all  going to be put together modular way to be   able to constitute the whole piece of software. Typically for software, popular design languages   are UML unified modeling language, SysML,...