More Related Content
What's hot (20)
Similar to Fundamentals of testing (20)
More from Siti Rubayati (13)
Recently uploaded (20)
Fundamentals of testing
- 1. Fundamentals of testing Siti Rubayati : 11453201587 Jurusan Sistem Informasi Fakultas Sains dan Teknologi Universitas Islam Negeri Sultan Syarif Kasim Riau
- 2. Welcome to Our Presentation The Power of PowerPoint | thepopp.com 2 One Column 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. Software systems context Not all software systems carry the same level of riskand not all problemshave the same impact when they occur . A risk is something that has not happened yet and it may never happen; it is a potential problem The Power of PowerPoint | thepopp.com 3
- 4. Causes of software defects The Power of PowerPoint | thepopp.com 4 3 columns 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. Not all defects result in failures; some stay dormant in the codeand we may never notice them.
- 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 Long text only The Power of PowerPoint | thepopp.com 5
- 6. Role of testing in software development, maintenance and operations The Power of PowerPoint | thepopp.com 6 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 7 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. Viewpoints of expectations and quality The Power of PowerPoint | thepopp.com 8 Viewpoint Software Tomatoes Quality is measured by looking at the attributes of the product. We will measure the attributes of the software, e.g. its reliability in terms of mean time between failures (MBTF), and release when they reach a specified level e.g. MTBF of 12 hours. The tomatoes are the right size and shape for packing for the supermarket. The tomatoes have a good taste and color. Quality is fitness for use. Quality can have subjective aspects and not just quantitative aspects. We will ask the users whether they can carry out their tasks; if they are satisfied that they can we will release the software. The tomatoes are right for our recipe. Quality is based on good manufacturing processes, and meeting defined requirements. It is measured by testing, inspection, and analysis of faults and failures. We will use a recognized software development process. We will only release the software if there are fewer than five outstanding high-priority defects once the planned tests are complete. The tomatoes are organically farmed. The tomatoes have no blemishes and no pest damage. Expectation of value for money, affordability, and a value-based trade-off between time, effort and cost aspects. We can afford to buy this software and we expect a return on investment. We have time-boxed the testing to two weeks to stay in the project budget. The tomatoes have a good shelf life. The tomatoes are cheap or good value for money. Transcendent feelings - this is about the feelings of an individual or group of individuals towards a product or a supplier. We like this software! It is fun and it's the latest thing! So what if it has a few problems? We want to use it anyway... We really enjoy working with this software team. So, there were a few problems – they sorted them out really quickly – we trust them. We get our tomatoes from a small local farm and we get on so well with the growers.
- 9. Defining software testing The Power of PowerPoint | thepopp.com 9 5 kLet's break the definition down into parts; the definition has some keyphrases to remember. The definition starts with a description of testing as aprocess and then lists some objectives of the test process. First, let's look attesting as a processeywords and descriptions 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. Process Preparation All life cycle activities Both static and dynamic Planning Evaluation Software products and related work products
- 10. Software test and driving test compared The Power of PowerPoint | thepopp.com 10 Both the examiner and the tester need a plan ofaction and need to prepare for the test, which is not exhaustive, but is representative and allows risk-based decisions about the outcome. Both dynamic (driving the car or executing the software) and static (questions to the driver or a review of the software) tests areuseful. The examiner and the tester must make an objectiveevaluation,log the test outcome and report factual observations about thetest. Determine that they satisfy specified requirements– The examiner and testerboth check against requirements to carry out particular taskssuccessfully. Demonstrate that they are fit for purpose - The examiner and thetester are notevaluating for perfection but for meeting sufficient of theattributes requiredto pass the test. Planning and preparation Purpose Static and dynamic Evaluation Requirements The examiner and tester both look for and logfaults.Detect defects
- 11. Sumber : Graham et.al (2011) 11 Thank you http://sif.uin-suska.ac.id http://fst.uin-suska.ac.id http://uin-suska.ac.id