Pass ISTQB CTFL Exam in First Attempt Easily

Introduction

1. About ISTQB [CC]

Icky has defined three levels of celebrity foundation, which is the target of this course advanced, which are test manager, Test Analyst and technical test analyst expert improving the testing processes, test management, test automation, engineering, security testing and so on. There’s a new extension for the foundation level called Agile Testing for those who are testing software in agile environment. Agile Testing is not in the scope of this course. It’s a separate curriculum and a separate exam and you don't need to know it to enter the Ice Cream Foundation Level Exam saying that the Ice-cream Foundation Level Certification is a prerequisite for the Ice Crab Agile Test Exam and the ISTQB Advanced Certificate Exam syllabi are written by testing experts and continuously reviewed, maintained and improved. The Foundation Level service is aimed at people with varying levels of experience in testing, including persons with no experience at all. It has been updated in 2010.This cost will always be based upon the latest sellers. The Foundation Level are classified according to its knowledge levels and there are four of them One remember where you need to recognize a term of a concept Two understand where you will need to be able to explain a concept case Three apply where you will need to select correct application of concept or technique for analyses where you can distinguish between facts and interfaces for deeper understanding. This doesn't mean that K One level is very easy nor a level is very difficult. The K leveled identifies the level of understanding being tested, not the difficulty of the problem.

2. About the ISTQB Foundation Level Exam [CC]

The ISTQB level exam is 1 hour long. The exam comprises of 40 multiple choice questions. All of the questions are of the same value. For every question there is only one answer that is correct. You don't get any negative marks if you answer any question incorrectly. So make sure you answer all the questions. You need to get 26 correct answers to pass the exam. The exam can be computer based or paper based depending on the exam provider. In your country, the breakdown of the questions could be fundamental of testing seven questions. Testing throughout the software lifecycle six questions. Static techniques three questions. Test design techniques twelve questions. Test management eight questions. Tools are both for testing four questions. Those numbers are approximate and the exact breakdown is not mandatory. But the exam will be closed to this proportion as far as possible. The breakdown of questions bear knowledge levels are50% of the questions will be of level one which is about 20 questions.30% of the questions will be K two level. So it's about twelve questions’ three and K four levels will hold20% of the questions which is eight questions. So it's not that bad at all. So it's not that bad after all. I’m sure you can do it. Good luck and enjoy the course. And please, if you have any questions just boasted there in the discussion board and I will answer it for you as soon as possible.

Hide

Important to know

1. What is Agile?

What is agile. Agile is definitely the latest and coolest buzzword in the software development world. These days. Everyone wants to be agile. But there are many misconceptions of what Agile means and many people don't fully understand the implications of what it takes to develop an effective agile development process. It’s very important to understand what we are getting ourselves into before taking any step. First, let's talk about the meaning of the word Agile. Dr.David Rico defined Agile as follows the ability to create and respond to change in order to profit in a tough global business environment. It’s also the ability to quickly reboot use of resources when requirements, technology and knowledge shift or exchange. It’s also a very fast response to sudden market changes and emerging threats by intensive customer interaction. Agile is use of evolutionary incremental and iterative delivery to meet an optimal customer solution. It’s also maximizing the business value with right size, just enough adjust in time processes and documentation. From the project management point of view, Agile is innovative software development but with more best practices to deliver a software with better quality at a lower cost in less time by highly motivated people. Wow, this is a big one. So let me iterative software development but with more best practices to deliver a software with better quality at a lower cost and less time by highly motivated people. We still use the same concept of iteration and continuous delivery of a working software to the customer after every iteration. Azure development has become commonplace in it industry. In a recent survey, over 52% of response said that their company practiced Agile development in one form or another. That’s something that I want you to know to notice, they said one form or another. Which means that there are different different forms tousle Agile in your project and we will talk about this in detail in future videos. So let's understand Agile from the first day it was born.

2. Agile Manifesto

In 2001, a group of very well-known names in the software industry representing the most widely used lightweight software development methodologies were logged in the software industry. How did they advance? And they didn't like what they see. They looked at the issues and came up with a solution which they called Agile. They agreed on a common set of values and principles which became known as the Manifesto for Agile Software Development or the Agile Manifesto. The way I look at the Agile Manifesto is as any country's constitution, this is the base that all the laws of that country should advise from. No law is allowed against the Constitution or the Manifesto. Let’s read it together. We are uncovering better ways of developing software by doing it and helping others do it. Though this work, we have come to value individuals and interactions over processes and tools. Working software over comprehensive documentation customer collaboration over contract negotiations responding to change over following plan that is while there is value in the items on the right, we value the items on the left more. The Agile Manifesto contains four statements of values. Let’s look at each one of them in detail. First one individuals and interaction over processes and tools. Software projects are people oriented. Much of our success is based upon effective interaction and communication. Even if we have the best processes and tools that combined with poor communication, success will be very likely. Processes and tools are well tools. They are not the objectives or the goals that we must follow. They are, after all, tools. Any processes and tools should be used as an enabler to increase the teamwork rather than replacing it. Projects are developed by people, problems get solved by people, scope is defined or negotiated by people and most importantly, projects are accepted by people. Focusing only on developing the individuals involved within the project and emphasizing productive and effective interactions help set up a project for success. Please note that this is not to say that Backhand tools cannot help in successfully completing a project. This is a common mistake done by companies who are starting to use Agile. They think Agile means no processes. Wrong. Our projects are ultimately about people. If we ask two teams to develop the same product, they will produce different outputs. Yes, it's the same software that helps with the same objective, but the requirement document will be different, the design will be different, the code will be different, and even how to test the software will be different. Everything will be different. Why? Because we depend on how people think, which varies from one person to another. Work in software over comprehensive documentation software without documentation is certainly a problem and will surely hold back support and maintenance. But comprehensive documentation without software is next to zero values to most organizations. Software projects are typically initiated with the goal of creating valuable high quality software, right? Even though this is very common sense it’s still we've been weeks or months writing extensive documentation that doesn't support the ultimate goal of creating software. From the customer perspective, working software is much more useful and valuable than very detailed documentations. In addition, because working software is available much area in the software development cycle, azure development can provide significant time to market advantage and it provides an opportunity to give the development team rapid feedback. I remember in my early days in the 80s when started to learn about waterfall I had to read like thousands of pages to understand what is the required documentation in waterfall and of course I had to create or reduce those thousands of pages of reports myself. Again, a very common mistake when people claim that Agile promotes no documentation wrong. This doesn't mean that we have to avoid documentation completely but only necessary documentation is reduced and for me this is an art to document only what is necessary. Do I need to document that the font used and we bought XYZ Times on New York? No, I can't see it. So why is it recoded in a document? So this means that valuable software will be delivered early and frequently during the development. So in Agile way of working, we deliver abuse of working software increment every iteration. That means we need to decide what to delivering every iteration and decide if a specific feature will add a value to the user or not. This value speaks about the need to deliver customer collaboration over contract negotiations. We all should know by now that customers often find great difficulty in specifying the system that they require and this is very natural. My friend, if you are a single person or when you were single, could you specify exactly what do you want in your future spouse? I doubt it. It's very hard to define exactly an unchanging view of what you want to build. Well, you see prototypes, you see this and that, you see different versions and then you can build from what you saw what you are actually looking for. So this value reminds us Tobe flexible rather than uncooperative. It’s similar to the difference between verification and validation verification during the thing right and validation during the right thing. Again, we value both verification and validation but we should value validation over verification. I will explain we could do verification and testing to build the product exactly as originally specified. But if the customer changes his mind or her minor claims that this will not help them and their business, it would be better to be flexible and work towards a new goal as opposed to the goal that was originally stated validation doing what the customer wants, verification doing it in the right way. Software products have a dynamic nature software is intangible, business needs change quickly, technology changes rapidly. Rather than beat up the customer or management with very tough change management to process we should recognize at the start that things are going to change and we should work with the customer throughout the project toward a shared understanding of how to define that something is done. Collaborating directly with the customer improves the likelihood of understanding exactly what the customer requires. Working in a regular and close collaboration with them is likely to bring more understanding and success to the project. Customers often do not know what they really want until they see something. Working. While having contracts with customers is important, agile boo motes are more trusting relationship and more flexible contract models than we often see on traditional projects. Writing contracts with the customer is a perfect motive and collaboration is a purpose motive. So purpose motive should be given more importance than profit motive. Responding to Changes over following a Plan so we agree that a change is inevitable in software projects. High rates of a change are common in software projects. Many factors might require that change. These factors must be accumulated by the development process. Also, the initial plans were made when we knew less about the project at the beginning of the project. And as the work progresses, we will learn more about the work and we should update the plan accordingly. The flexibility to accommodate changes into the blend is more significant than just writing blend and following i.e. need to acknowledge that things will change and blend smoothly again and again. This doesn't mean that Azure Manifesto is suggesting that we abandon blending and just to react to changes. No, we still need to plan, but we need to plan smartly. So the Azure Manifesto guides us to consider projects from a value based perspective. Yes, we will need processes, tools, documentation and blends on our budgets. Yet while dealing with those assets, we should remember that our focus must be on the people engaged the product that we are building. Cooperation and Flexibility agility is the ability to execute broad projects while focusing our efforts on the items on the left in the Azure Manifesto over the items on the right.

3. Scrum

Scrum is another agile development framework that has several key features that are shown in the figure and we will explain each one of them in details. Three rules the Scrum master who ensures that Scrum practices and rules are understood, implemented and followed and resolves any violation, resource issues or other barriers that could prevent the team from following the practices and rules. This person is not the team leader, but a coach. For me, I consider him more of a quality assurance person, but that's only my point of view. Product Owner represents the customer who is responsible for maximizing the value of the product has the sole responsibility of managing the product backlog, including its bio atomization, accuracy, shared understanding, value and visibility. Again, this Bellson is not the team leader. Development team is a group of professionals who can fulfill all the roles needed to complete the work and build the product increments. In each iteration, the development team is empowered to manage its own work and its members are self-organizing and cost functional. They develop and test the product. Again, there is no team leader, so the team makes its own decisions. Scrum contains the following instruments and practices a Scrum divides a project into iterations of fixed lens Cold, Sprints and Scrum, and the lenses usually two to four weeks. Every iteration should attempt to build potentially shapeable and properly tested product increment. The time duration for this brand and how long it lasts is decided by the team based on their requirements and capabilities. Brand duration, once agreed upon, should not be modified, which means if anything unusual happened during the Sprint that requires extra time, it should be moved to the next Sprint. A Sprint is like a mini project. During the Sprint, no changes are made that would affect the Sprint goal, although the scope may be clarified or renegotiated as new information becomes available. Each sprint includes as print planning meeting, daily scrums development work, as print review meeting and as print retrospective. We will talk about those events in future lectures. The development team members are kept the same throughout the Sprint product. Each Sprint results in a potentially reusable shippable product called an increment product. The product owner manages a paretorized list of blend product items in a lock called the product backlog. The product backlog is an ordered list of everything that might be needed for the product to be built. The product backlog serves as the single source for requirement. It is dynamic and evolves as the product evolves from Sprint to Sprint. Called backlog refinement, it contains features to be built, functions, requirements, nonfunctional requirements and fixes, and whatever needs to be done is idly expressed such that each item has value to the users or customers of the product. The product backlog bout Aries by the product owner and refined at the start of each iteration. Grooming is the process of adding more detail and order to the backlog and refining the estimates of the backlog items backlog at the start of each brand, the Scrum team selects a set of the highest priority items from the product Bear Clog and put it into the Sprint Bear Club, combined bay plan of how to achieve the Sprint goal. Since the Scrum team, not the product owner, selects the items to be realized within the Sprint, the selection is referred to as being on the pull principles rather than the push principle principles. The developer is pulling the items from the product backlog and put it in the print backlog and not the product owner bushes the item against the developers. The print backlog may only be updated by the development team. Definition of Done the team should collectively create the definition of don for the items before they begin to work on them. This helps to make sure that there Isa potentially reliable product at each brand’s. End the Scrum team discusses and defines appropriate criteria for his brain's completion. The discussion deepens the team's understanding of the backlog items and the product requirements. Time Boxing time boxes are short fixed duration periods of time in which activities of work are undertaken. If the work blend for the time box is not complete when the time runs out, then we stop what we are doing and move the uncompleted work into another time box. Examples of time boxes include daily standard meetings that are time boxed to 15 minutes, iterations that are time boxed to typically two weeks, and so on. As we mentioned before, only those tasks, requirements or features that the team expects to finish within the Sprint are part of the Sprint backlog. If the development team cannot finish a task within a Sprint, the associated product features are removed from the print and the task is moved back into the product backlog. Transparency the development team reports and update sprint status on a daily basis ate meeting called the Daily Scrum. This makes the content and the progress of the current brand, including test results which should be visible to the team management and any interested party. For example, the development team can show his brain to status on a whiteboard. It’s so simple. Unlike XP, the Scrum does not dictate specific software development technique like pair programming, nor test first programming. In addition, Scrum does not provide guidance on how testing has to be done in a Scrum.

Hide

Fundamentals of Testing

1. Software Systems Context [CC]

You. Software applications are everywhere and they became a crucial part of our lives. Every one of us has used software in one way or another. You can see software in many apps on your phone, medical machinery, in hospitals, in your car or airplanes, in business applications like banking and stock market, and even in entertainment where all your favorite movies are made using software. Software that doesn't work or even have minor problems might cause huge problems and frustrations. A small miscalculation in a business application might cause loss of money. Early software operation or slow report might waste time and causes frustration. If you are waiting online for your turn ate cashier, your business reputation will be in jeopardy if your software is not up to standards and could even cause injury or death. There are many examples of a minor software issues that cause huge problems. I will just show you one of the very famous problems that was the first launch of the European Space Agency area Five rocket in June 1996 failed after 37seconds, which caused the loss of millions of dollars. After investigation, the problem came down to single step in the software that causes the software to crash, a hardware to crash and then the whole rocket to crash. So taking care of creating a good, stable, functional software should be our goal. Moreover, no issues in a software is a small issue. I have seen software projects fail because of a minor single taboo in one of the screens of the software. When the customer saw the taboo after delivering the software, he cancelled his future work with that company. He said that if they didn't catch an obvious problem like this one, how would they discover hidden problems in the software?

2. Causes of Software Defects [CC]

So why are there are defects in the software? After all, software is created by human and human make mistakes. It doesn't have to be because they are lazy or ignorant. People make mistakes because they are imperfect. But there are also many pressures that make mistakes. More likely, if a document with an error in itis used to specify a component, then the component will be faulty and will probably exhibit incorrect behavior. The error in the document could be the system analyst mistake or the customer mistake in the first place. Pressures such as deadlines, complexity of systems and organizations, and the changing technology all bear down on designers of systems and increase the likelihood of errors in the specification, in designs, and in the software. Code errors also can arise duet noncompliance with required standards. For example, combined standard tests, safety critical or safety related, such as reload switching, air traffic control, and so on. Let’s now look at some important definitions. A human being can make an error mistake. This person could be the system asked designer or coder of the system, or even the customer or users. Some of those errors will add a defect fault or bug in the programmer code or in a document. I said some of those errors because not all mistakes will produce a bug. An analyst mistake would add a bug to the software, but user mistake will not add a bug to the software. If a defecting code is executed, the system may fail to do what it should door do something it shouldn't, causing a failure. Again, notice that I said may fail because not all defects would fail the software. Actually, some bugs would only cause the software to fail under very specific circumstances. If those circumstances would never happen, then the defect will not cause a failure. There is a saying to error is a human. To find the error requires a testing.

3. Role of Testing in Software Development, Maintenance and Operations [CC]

If the defects found are corrected before the system is released for operational use. Testing of systems and documentation can help to reduce the risk of problems occurring during operation and contribute to the quality of the software system. Notice here that this course is talking about testing as a role, not as a job, which means that the course is talking about testing from the point of view if anyone helps making the software a better quality. So in this course, the developer is attester, the budget manager is a tester, and even the customer is a tester. That’s of course, in addition to the system whose main job is testing the software, which we will sometimes refer to as system tester. To highlight that distinction, software testing purpose may not only be to find effects, but it may also be required to meet contractual or legal requirements or industry specific standards. Now think for a second what system distance finds errors, bugs or failures.

Hide