ISTQB FOUNDATION 4.0 | Tutorial 9 | Sample Questions on Chapter 1 | ISTQB Foundation Sample Question

Hello friends and greetings for the day welcome back to another tutorial on istqb Foundation level certification we are in chapter 1 and we are done with all the tutorials of this particular chapter but shall be looking forward to have discussions on some of the sample questions from this chapter to understand how exactly the expected questions look like and what could be the best way to tackle them to get to the right answers well to get started with the very first question we have here on the screen is to talk about that which of the following

statements describe a valid test objective now we must at this point recall quickly that what exactly are those common test objectives which we have with respect to the test specifications and we must look forward to recall them in order to get the right answer number one and most important tip at this point of time I would like to share is always try to get your answer first within your mind from your learnings and then look at the options because sometimes the options are a little tricky and if you start reading the options without bringing in

your own result you may get confused and get to the wrong answer also so it is very important that you look forward to start talking about your learning first and once you have some conclusion in your mind then look at the options so right the options here are option A to prove that there are no unfixed defects in the system under test I think that's a contradictory statement with respect to principle number one the principle one said that testing is just to show the presence of defect but cannot prove the absence of defect and that

certainly becomes a big challenge to say as one of the objective of testing it's not one of the objective of testing and certainly cannot be taken for granted always so the second option what we have is option b and that option b is talking about to prove that there will be no failures after the implementation of system into production now after that is like when we talk about the absence of error fallacy it is of course something which we are trying to build up but it may not be something which I can go and promise

you that the failures will not result into any kind of drawbacks so if you look into the statement right here it clearly says that to prove that there will be no failures after the system which is again contradicting with our principle 1 and principle 7 as well principle 7even in the sense like absence of error fallacy I may just find and fix defects but if the requirements are not fulfilled it may not make any sense so as far as I have met the requirements I may not go and tell you that what other failures will

happen but if in case anything happens I cannot be ass sure or confident about that that will not result into a failure so I cannot make any such statement as one of the key objectives of testing when I talk about that option C and we are talking about here we have to reduce the risk level of the test object and to build confidence in the quality level that certainly is one of the key objectives what we have discussed and learned about that as a part of testing we try to first of all of course we

have risk identification process taking place which helps us to identify the risk areas and then proportionate amount of testing is being conducted to mitigate those risks sometime we don't just mitigate everything but we do bring down the level of risk and certainly to gain confidence about the quality of the product right so that's one of the key objectives but just cross check with option D the option D is saying to verify that there are no untested combination of inputs I think contradicting with principle number two principle number two says exhaustive testing is impossible and there

we say that we cannot just try everything a set of combinations in order to test a particular scenario so that's not something which is very very straightforward to say that you have to check that there are no untested combinations because there would be many as we do not test everything what comes into the permutation and combination so in that context when we look at all the four options once again the right answer here is C to reduce the risk level of test objects and to build confidence in the quality level is one of the valid

objectives of testing well look Ming on the the next question the question number two what we have here for you is you have been assigned as a tester to a team producing a new system incrementally you have noticed that no changes have been made to existing regression test cases for a several iteration and no new regression defects were identified your manager is happy but you are not which testing principle explains your skeptism now of course I think we are pretty much aware what exactly is being discussed but I don't want to give you that straightforward

rather assume that even I'm not sure what exactly they're talking about the most important thing what they're discussing in this particular question is number one that they are referring to things which are following a methodology of agile and second important thing they highlighted that your existing regression test cases or regression test Suite has not been revised over a period of time and I think right at this point I should quickly come back to the principles of testing and should think about one of the princip which talks about tests we out which clearly talks about that

pesticide Paradox that means you there's no point using the same test cases again and again as far as the product evolves over a period of time so as the code is changing every single iteration because the methodology is agile every single Sprint new code is being added it is certainly something which I should keep revising over a period of time a manager may be happy is just a diversion for you sometimes some statements you do find which which are just a tricky one to give you a diversion so that you start thinking about it rather

than concentrating on the answer so let the manager be happy because we are progressing well but even if that doesn't happen I don't care about it because they are talking about the principles here not about who should be happy right so in that context I think the things which comes to our mind is the pesticide Paradox and also called as test wear out so let's quickly check out which option is that and I'm I think we would have already got the answer here so we have option A tests wear out which is pesticide Paradox B

absence of error fallacy C defects cluster together D exhaustive testing is impossible and I think we have already discussed what should be the right answer here so the right answer is a tests wear out is the right principle what we are talking about when it comes to revision of test cases especially the regression test Suite moving on to the next question which is question number three and here we are talking about another situation which is talking from the perspective of the test process context and the factors influencing that so the question says which of the

following factors that is first to five have significant influence on the test process so here we need to just consider those important things which will significantly that means more importantly being concerned towards the test process influenc right so maybe sometime you will get those options which are pretty much look correct but when the word significant is used uh it must be considered from the perspective of that you know which are the important ones not everything so in that context let's have a look on the five steps here so we have the first one as the

sdlc of course that's one of the key criterias which drive your test process to the number of defects detected in previous project that could be a good reference for us but not necessarily uh something which influenc the test process because entire testing is all about uh finding defects so the number of defects detected in previous projects may have some influence but not something which drives the overall process so significantly that's not something what I would take into account not I everyone should not take that into account number three the identified product risk of course that's

a key contributor to overall test process because as far as you have the product identified you need to look forward to mitigate them as much as possible so it's a key factor to take into account to Define your test process which we'll be looking forward to mitigate them and when I talk about number four the new regulatory requirements forcing formal white box testing now that's another interesting thing which is uh number four it is the regulatory requirement without which if in case you fail to fulfill these regulatory contractual and standard driven requirements then maybe your

product may not go Al and that could be a big challenge for the organization at the end of the day so yes I should consider that also as one of the parameter and fifth the test environment setup I think the test environment setup is something which basically happens as a part of the requirement of the business and the product and that has nothing to drive your test process so it does not have significant influence as a part of the process but yes it is one of the activity which we do conduct but it does not

drive the process as such right so in that context put together we have four options so option A says one and two have significant influence no two is not considered as one of the relevant one B 134 looks correct c 2 4 and five can be ruled out and D 3 and 5 can be ruled out so I think put together the right answer here is B where it is saying first third and fourth fourth which means the sdlc the identified product R and the regular requirements are certainly one of the significant contributors from the

given list of course we do have many but from the given list these are the three items which are significantly going to influence your test process so that's all from these sample questions team of course we do know there are many other so we'll be creating a separate playlist later after this to guide you with all other sample questions with explanation but for now these three papers are but this D sample questions are just enough so you should get an idea from here more importantly the knowledge is more significant to get to the right answer

so that's all from this particular tutorial team should you have anything else feel free to comment below I'm 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 [Music]