Hello friends and greetings for the day welcome back to another tutorial on istqb Foundation level certification we are in Chapter 2 talking about testing throughout this DLC and we are done with all the topics and it's time for us to quickly look at some of the sample questions from this chapter in order to understand what is expected when it comes to the examination all right so to get started of course we have the very first question to talk about today is on your screen right now and that is consider the following rule for every sdlc activity there's a corresponding test activity I think we can recall quickly here that uh there are four standard characteristics or good characteristics of testing and one among them has been mentioned here that is for every sdlc activity which is development activity there is a corresponding test activity now in which sdlc model does this rule hold I think uh as usual when I told you that when it comes to uh any type of questions to solve them when the context has been given to you in the question you don't really have to look at the options but be upfront to get your own answer first recall your knowledge recall your understanding about that particular topic and get to your answer only if you are confused then the option should help you or you should look at it but when you are pretty much prepared you know that what you have learned what you have been through then pick up your answer first and get to the conclusion and then look at the options otherwise the options could be sometime very tricky so we have our answer already that is it is applicable to any development model it is not restricted to any development particular development model but applies to any development model so that's what the answer should be but let's look at the options what we have here with us so option A says only in sequential sdlc model which is of course Incorrect and that does not apply only to sequential development models B only to iterative sdl models no that's just not limited to that c only in iterative and incremental sdlc models answer is no that's again not it is to any development model and in that context when we come to option D it says in sequential incremental and I TR as DLC model and uh in that context if we give it up Al together the right answer here is D in sequential incremental and alterative SD sdlc models it is applicable so put together I think uh that's how sometime we can be very very straightforward to pick up our very right answer subjected you know the context and content better so let's look at the next question here the next question is question number two and that says which of the following is not an example of the shift left approach now shift left approach if you remember from our discussions we told you that shift lift approach is all about preponing the activities to that of the traditional and conventional way of doing those activities for example if you're planning to execute a test generally in test executions then you are trying to preone some of the executions a little early to different levels or preparing a test particularly much earlier than the desired phase of writing the test case so whenever you preone something or preone an activity or a particular EX execution just with certain consideration like complexity risk factor Etc you call it as shift left approach so today the things are about prevention not just limited to execution so they are talking about the word not here which is very very crucial the word not certainly talks about what is not that means they are inverse that means three options will be talking about what is shift left approach and one option will be talking about what is not right so many people during the examination do not concentrate on the word not because it's very easy to skip that and talk about shift left approach that is the subject so make sure that you do not ignore the word not while reading the questions you should read every single word carefully and come to the conclusion that what exactly they want to know so here it is completely driven by the options and we cannot make a decision or conclusion that what is true what is not so let's look at the options here option A says reviewing the user requirement before they are formally accepted by stakeholders I think that's pretty much uh the shift left approach this is not something which is not because here you are reviewing that means you are conducting a kind of testing that is static testing of the user requirements before they are formally accepted so a round of testing has been conducted and that is certainly shift left approach talking about B writing a component test before the corresponding code is written so of course you can understand code is written then you write a test but if you're writing a test before the code is written it's preponing so it is shift left approach C executing a performance efficiency test for a component during component testing because performance testing is something which is generally executed or conducted after the system is stable so it should be done generally after system testing level and mainly it is done after that but if you are conducting a small performance test during component test level which is much earlier than system testing it is again a shift left approach which is preponing right now let's look at the option D I think we just left with that but still let's confirm what exactly it is so D says writing a test script before setting up the configuration management process of course configuration management process executes your test right and writing a test script before that is not preponing right you will have to write the tests all together first and then you have to put it in the pipeline which is more of like configur ation management or devops so certainly until the scripts are written what would you feed into the pipeline or devops so to execute it so in that context of course uh that's not something which is talking about preponing and that's limited to uh the generic process so put together the right answer here is D which means writing a test script before setting up the configuration management process is not an example of sh shift left approach moving on to the third question let's have a quick look here and this is going to take a little while to understand uh it says you are testing a user story with three acceptance criteria namely ac1 ac2 AC3 where ac1 is covered by test case 1 ac2 is covered by test case 2 AC3 by TC3 the test execution history had three test runs on three consecutive versions of the software as follows that means the test test was executed twice uh like three different times and uh respectively these are the outcomes which are given to you in the table right on your screen now the question is tests are repeated once you are informed that all the defects found in the test runs are corrected and the new version of software is available I think that's a very generic process of uh reporting a effect getting it retested and then just to confirm that due to this fix nothing has changed is we conduct regression testing so here in this particular table all they're trying to tell you is that you know these are the backto back executions which happen for three test cases and uh the operation was retesting and regression testing now which of the above tests are executed as regression test so when they told you that there are reported defs on failure then of course you will conduct it as retesting but which ones are conducted as regression so the first and foremost thing is to define the definition of regression testing regression testing is a reputation of test which has already passed in past and we are executing it once again to confirm there are no side effects they're still continuing to work as expected so it's not necessary that they failed earlier they passed earlier and now again we are trying to run it to make sure that they still pass that's the on line definition to regression so first of all uh without looking at the options here you don't need the options of course you need the table and you have to make your own judgment so if you look at the table execution one the test case 1 and test case 3 has failed reporting a defect whereas test case 2 passed that means it was working fine so I reported a defect for test case 1 and test case 3 now they have fixed this particular version and sent you a new one and you did execution two in execution two the test case one passed which means retesting passed the defect has been resolved whereas test case 2 has failed which is initiating a new defect and certainly uh uh test case 3 continued to fail that means the defect has not been fixed yet so test case 2 is absolutely fine but the reason I re-executed test case 2 is to confirm the regression right because in execution one it already passed so I repeated this execution just to confirm but good that I found that regressions were introduced so number five is a good candidate for us to say that it was repeated as a part of regression because earli it passed this time we executed it failed okay so running a pass test case once again is regression and five is a good candidate for us uh whereas other two were failed so I had to do retesting for that that's not regression and execution three again they fixed it so if you in case you see this here the four actually passed in execution test sorry test case one passed in execution two and uh execution 3 I repeated it to confirm the regression so seven is regression whereas five and six actually failed so I repeated it to confirm the retesting okay so in that context if I pick up my answer the right answer here should be B only five and seven are executed in terms of regression whereas all other are conducted in form of retesting okay so put together I hope we got a very good understanding of this in case the last question was slightly unclear please revisit and relisten to the conversation you will get it because I've just did it did it step by step to make sure that you have a wonderful understanding of that so that's all from this particular tutorial team should you have anything else feel free to comment below I'll be always there to address your queries and answer them well till then keep learning keep exploring keep understanding the context thanks for watching the video team and happy [Music] learning