Fundamentals of testing
Download as PPTX, PDF0 likes46 views
The document discusses the fundamentals of software testing, emphasizing the importance of identifying defects throughout the software development life cycle to prevent failures. It highlights the roles of human errors and flaws in software design as causes of defects, as well as the necessity for rigorous testing to achieve software quality. Additionally, it addresses the differing perceptions of quality between developers and customers and outlines the testing process and management activities involved in software testing.
Fundamentals of testing
- 1. FUNDAMENTALS OF TESTING Jurusan Sistem Informasi Fakultas Sains dan Teknologi Universitas Islam Negeri Sultan Syarif Kasim Riau FAJAR AYU NINGRUM
- 2. Software systems context Causes of software defects Role of testing in software development, maintenance and operations Testing and Quality Viewpoints of expectations and quality Defining software testing Software test and driving test compared
- 3. Not all software systems carry the same level of riskand not all problemshave the same impact when they occur . Software systems context A risk is something that has not happened yet and it may never happen; it is a potential problem
- 4. Causes of software defects Error If someone makes an error or mistake in using the software, this may leaddirectly to a problem - the software is used incorrectly and so does not behaveas we expected Defects However, people also design and build the software and theycan make mistakes during the design and build. These mistakes mean that thereare flaws in the software itself. These are called defects or sometimes bugs orfaults. Remember, the software is not just the code; check the definition of soft-ware again to remind yourself Failure When the software code has been built, it is executed and then any defects maycause the system to fail to do what it should do (or do something it shouldn't),causing a failure
- 5. but itis difficult for people to find their own mistakes while building a product. that if a mistake does not lead to adefect or a defect does not lead to a failure, then it is not of any importance -we may not even know we've made an error . Our fallibility is compounded when we lack experience, don't have the rightinformation, misunderstand, or if we are careless, tired or under time pressure . Additionally, we are more likely to make errors when dealing with perplexing technical or business problems, complex business processes, code or infrastructure, changing technologies, or many system interactions Slide Title Goes Here
- 6. Role of testing in software development, maintenance and operations Role of testing in softwarWe have seen that human errors can cause a defect or fault to be introduced atany stage within the software development life cycle and, depending upon theconsequences of the mistake, the results can be trivial or catastrophic. Rigoroustesting is necessary during development and maintenance to identify defects, inorder to reduce failures in the operational environment and increase the qualityof the operational system. This includes looking for places in the user interfacewhere a user might make a mistake in input of data or in the interpretation ofthe output, and looking for potential weak points for intentional and maliciousattack. e development, maintenance and operations
- 7. TESTING AND QUALITY Testing Testing can give confidence in the quality of the software if it finds few or no defects, provided we are happy that the testing is sufficiently rigorous . Of course, a poor test may uncover few defects and leave uswith a false sense of security Quality We need to understand what the customers understand by quality andwhat their expectations are. What we as software developers and testers maysee as quality – that the software meets its defined specification, is technicallyexcellent and has few bugs in it – may not provide a quality solution for our customers. Furthermore, if our customers find they have spent more money thanthey wanted or that the software doesn't help them carry out their tasks, theywon't be impressed by the technical excellence of the solution
- 8. Evaluation Process All life cycle activities Both static and dynamic Planning Preparation • Testing is a process rather than a single activity– there are a seriesof activities involved. • Chapter 2 looks at testing as a process that takesplace throughout the software development life cycle. We saw earlierthat the later in the life cycle we find bugs, the more expensive they areto fix. • We'll see in Chapter 3 that as well as tests wherethe software code is executed to demonstrate the results of running tests(often called dynamic testing) we can also test and find defects without executing code. • Activities take place before and after test execution We need tomanage the testing; for example, we plan what we want to do; we control thetest activities; we report on testing progress and the status of the softwareunder test; and we finalize or close testing when a phase completes • We need to choose what testing we'll do, by selecting test conditions and designing test cases. Chapter 4 covers the test design activities.
- 9. TENGKYU..