DOCSLIB.ORG

Scenario Testing

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Scenario Testing Scenario Testing Prepared By S.Rijutha AP/IT 1 IT6004/ST/Unit-3 What is it? set of realistic user activities that are used for evaluating the product. Testing involves customer scenarios Methods System Scenarios Use case Scenarios Step wise procedure on Testing covers several how a user intends to use components in the system the system 2 IT6004/ST/Unit-3 System Scenarios Story line Life cycle/state transitions Deployment/implementation stories from customer Business verticals Battle ground 3 IT6004/ST/Unit-3 Story line Develop a story line that combines various activities of the product that may be executed by an end user. A user enters his or her office, logs into the system, checks mail, responds to some mails, compiles some programs, performs unit testing and so on. 4 IT6004/ST/Unit-3 Life cycle/state transitions Consider an object, derive the different transitions/modifications that happen to the object, and derive scenarios to cover them. For example, in a savings bank account, you can start with opening an account with a certain amount of money, make a deposit, perform a withdrawal, and calculate interest, and so on. 5 IT6004/ST/Unit-3 Deployment/implementation stories from customer Develop a scenario from a known customer deployment/implementation details and create a set of activities by various users in that implementation. 6 IT6004/ST/Unit-3 Business verticals Visualize how a product/software will be applied to different verticals and create a set of activities as scenarios to address specific vertical businesses. For example, take the purchasing function. It may be done differently in different verticals like pharmaceuticals, software houses, and government organizations. Visualizing these different types of tests make the product "multi- purpose." 7 IT6004/ST/Unit-3 Battle ground Create some scenarios to justify that "the product works" and some scenarios to "try and break the system" to justify "the product doesn't work." 8 IT6004/ST/Unit-3 The set of scenarios developed will be more effective if the majority of the approaches mentioned above are used in combination, not in isolation. Scenario should not be a set of disjointed activities which have no relation to each other. Any activity in a scenario is always a continuation of the previous activity, and depends on or is impacted by the results of previous activities. A right mix of scenarios using the various approaches explained above is very critical for the effectiveness of scenario testing. 9 IT6004/ST/Unit-3 Coverage of activities by scenario testing 10 IT6004/ST/Unit-3 Use Case Scenario A use case scenario is a stepwise procedure on how a user intends to use a system, with different user roles and associated parameters. A use case scenario can include stories, pictures, and deployment details. Actors • Users with different roles • What the product should do for a particular system behavior activity • Users with a specific role to interact between the Agents actors and the system 11 IT6004/ST/Unit-3 Example needs to be tested not concerned about before applying the the logic of how the sequence of agent computer works Agent activities and actor activities. Query Cheque System Actor Response Need not know what the Response official is doing and what command he is using to Cash interact with the computer. 12 IT6004/ST/Unit-3 Actor and System response in use case for ATM cash withdrawal Use cases are useful for explaining customer problems and how the software can solve those problems without any ambiguity. Actor System response Users likes to withdraw cash and inserts the Request password or PIN card in the ATM machine User fills in the password or PIN Validate the password or PIN Give a list containing types of accounts User selects an account type Ask the user for amount to withdraw User fills in the amount of cash required Check availability of funds Update account balance Prepare receipt Dispense cash Retrieve cash from ATM Print receipt 13 IT6004/ST/Unit-3 This way of documenting a scenario and testing makes it simple and also makes it realistic for customer usage. Use cases are not used only for testing. In some product implementations, use cases are prepared prior to the design and coding phases, and they are used as a set of requirements for design and coding phases. All development activities are performed based on use case documentation. In extreme programming models these are termed as user stories and form the basis for architecture/design and coding phases. Hence, use cases are useful in combining the business perspectives and implementation detail and testing them together. 14 IT6004/ST/Unit-3 Defect Bash 15 IT6004/ST/Unit-3 Defect Bash Defect bash is an ad hoc testing where people performing different roles in an organization test the product together at the same time. This is very popular among application development companies, where the product can be used by people who perform different roles What is to be tested is left to an individual's decision and creativity 16 IT6004/ST/Unit-3 Brings in the Good practices Cross boundaries and test beyond assigned areas Testing isn't for testers alone Letting everyone in the organization use the product before delivery— "Eat your own dog food" Fresh eyes have less bias Users of software are not same Does testing wait till all documentation is done? Testing isn't to conclude the system works or doesn't work 17 IT6004/ST/Unit-3 Steps involved Step 1 • Choosing the frequency and duration of defect bash Step 2 • Selecting the right product build Step 3 • Communicating the objective of each defect bash to everyone Step 4 • Setting up and monitoring the lab for defect bash Step 5 • Taking actions and fixing issues Step 6 • Optimizing the effort involved in defect bash 18 IT6004/ST/Unit-3 Step 1 • Choosing the frequency and duration of defect bash Defect bash is an activity involving a large amount of effort and an activity involving huge planning Frequent defect bashes low return on investment, and too few defect bashes may not meet the objective of finding all defects. Duration is also an important factor. Optimizing the small duration is a big saving as a large number of people are involved. On the other hand if the duration is small, the amount of testing that is done may not meet the objective. 19 IT6004/ST/Unit-3 Step 2 • Selecting the right product build A good quality build is needed for defect bash. gives confidence on the product and progress A regression tested build would be ideal as all new features and defect fixes would have been already tested in such a build. An intermediate build where the code functionality is evolving or an untested build will make the purpose and outcome of a defect bash ineffective. Also, when testers doing a defect bash uncover an excessive number of defects or very severe defects, the confidence of the tester’s falls and the perception of the product being unstable linger on for long. 20 IT6004/ST/Unit-3 Step 3 • Communicating the objective of each defect bash to everyone The objective should be to find a large number of uncovered defects or finding out system requirements (CPU, memory, disk, and so on) or finding the non-reproducible or random defects, which could be difficult to find through other planned tests. Once they are told in advance, the members of defect bash team will be in a better position to contribute towards stated objectives. 21 IT6004/ST/Unit-3 Step 4 • Setting up and monitoring the lab for defect bash Finding out the right configuration, resources (hardware, software, and set of people to perform defect bash) are activities that have to be planned carefully before a bash actually starts. Right Set up is done- most critical to ensure Else test fails 22 IT6004/ST/Unit-3 During defect bash, the product parameters and system resources (CPU, RAM, disk, network) need to be monitored for defects and also corrected so that users can continue to use the system for the complete duration of the defect bash. However, if the lab is not set up properly or not monitored properly, there is a chance that some of the non-functional defects may not get noticed at all. memory leak, long Types of defects turnaround time, that are in the missed requests, product, as high impact and utilization of system reported by the Non Functional Functional Defect resources users Defect 23 IT6004/ST/Unit-3 Step 5 • Taking actions and fixing issues different interpretations of the same defect by different users It is difficult to solve all the problems if they are taken one by one and fixed in code Classification of defect need to be done. Defect associated with issue. All the issues reported from a defect bash need to be taken through a complete code and design inspections, analyzed, and fixed together in places where a defect could evolve from. 24 IT6004/ST/Unit-3 Step 6 • Optimizing the effort involved in defect bash Keeping the right setup, sharing the objectives, and so on, to save effort and meet the purpose have been already discussed. Conduct micro lever defect bashes before conducting one on a large scale. Defect Bash Feature/component Integration defect Product defect bash defect bash bash 25 IT6004/ST/Unit-3 Three product defect bashes conducted in two hours with 100 people Total effort involved is 3*2*100= 600 person hours. If the feature/component test team and integration test team, that has 10 people each, can participate in doing two rounds of micro level bashes, which can find out one third of defects that are expected, then effort saving is 20% with respect to the following calculation.
Load more

Recommended publications
  • A Combinatorial Approach to Detecting Buffer Overflow Vulnerabilities
    A Combinatorial Approach to Detecting Buffer Overflow Vulnerabilities Wenhua Wang, Yu Lei, Donggang Liu, David Raghu Kacker, Rick Kuhn Kung, Christoph Csallner, Dazhi Zhang Information Technology Laboratory Department of Computer Science and Engineering National Institute of Standards and Technology The University of Texas at Arlington Gaithersburg, Maryland 20899, USA Arlington, Texas 76019, USA {raghu.kacker,kuhn}@nist.gov {wenhuawang,ylei,dliu,kung,csallner,dazhi}@uta.edu Abstract— Buffer overflow vulnerabilities are program defects Many security attacks exploit buffer overflow vulnerabilities that can cause a buffer to overflow at runtime. Many security to compromise critical data structures, so that they can attacks exploit buffer overflow vulnerabilities to compromise influence or even take control over the behavior of a target critical data structures. In this paper, we present a black-box system [27][32][33]. testing approach to detecting buffer overflow vulnerabilities. Our approach is a specification-based or black-box Our approach is motivated by a reflection on how buffer testing approach. That is, we generate test data based on a overflow vulnerabilities are exploited in practice. In most cases specification of the subject program, without analyzing the the attacker can influence the behavior of a target system only source code of the program. The specification required by by controlling its external parameters. Therefore, launching a our approach is lightweight and does not have to be formal. successful attack often amounts to a clever way of tweaking the In contrast, white-box testing approaches [5][13] derive test values of external parameters. We simulate the process performed by the attacker, but in a more systematic manner.
    [Show full text]
  • Types of Software Testing
    Types of Software Testing We would be glad to have feedback from you. Drop us a line, whether it is a comment, a question, a work proposition or just a hello. You can use either the form below or the contact details on the rightt. Contact details [email protected] +91 811 386 5000 1 Software testing is the way of assessing a software product to distinguish contrasts between given information and expected result. Additionally, to evaluate the characteristic of a product. The testing process evaluates the quality of the software. You know what testing does. No need to explain further. But, are you aware of types of testing. It’s indeed a sea. But before we get to the types, let’s have a look at the standards that needs to be maintained. Standards of Testing The entire test should meet the user prerequisites. Exhaustive testing isn’t conceivable. As we require the ideal quantity of testing in view of the risk evaluation of the application. The entire test to be directed ought to be arranged before executing it. It follows 80/20 rule which expresses that 80% of defects originates from 20% of program parts. Start testing with little parts and extend it to broad components. Software testers know about the different sorts of Software Testing. In this article, we have incorporated majorly all types of software testing which testers, developers, and QA reams more often use in their everyday testing life. Let’s understand them!!! Black box Testing The black box testing is a category of strategy that disregards the interior component of the framework and spotlights on the output created against any input and performance of the system.
    [Show full text]
  • Scenario Testing) Few Defects Found Few Defects Found
    QUALITY ASSURANCE Michael Weintraub Fall, 2015 Unit Objective • Understand what quality assurance means • Understand QA models and processes Definitions According to NASA • Software Assurance: The planned and systematic set of activities that ensures that software life cycle processes and products conform to requirements, standards, and procedures. • Software Quality: The discipline of software quality is a planned and systematic set of activities to ensure quality is built into the software. It consists of software quality assurance, software quality control, and software quality engineering. As an attribute, software quality is (1) the degree to which a system, component, or process meets specified requirements. (2) The degree to which a system, component, or process meets customer or user needs or expectations [IEEE 610.12 IEEE Standard Glossary of Software Engineering Terminology]. • Software Quality Assurance: The function of software quality that assures that the standards, processes, and procedures are appropriate for the project and are correctly implemented. • Software Quality Control: The function of software quality that checks that the project follows its standards, processes, and procedures, and that the project produces the required internal and external (deliverable) products. • Software Quality Engineering: The function of software quality that assures that quality is built into the software by performing analyses, trade studies, and investigations on the requirements, design, code and verification processes and results to assure that reliability, maintainability, and other quality factors are met. • Software Reliability: The discipline of software assurance that 1) defines the requirements for software controlled system fault/failure detection, isolation, and recovery; 2) reviews the software development processes and products for software error prevention and/or controlled change to reduced functionality states; and 3) defines the process for measuring and analyzing defects and defines/derives the reliability and maintainability factors.
    [Show full text]
  • A Test Case Suite Generation Framework of Scenario Testing
    VALID 2011 : The Third International Conference on Advances in System Testing and Validation Lifecycle A Test Case Suite Generation Framework of Scenario Testing Ting Li 1,3 Zhenyu Liu 2 Xu Jiang 2 1) Shanghai Development Center 2) Shanghai Key Laboratory of 3) Shanghai Software Industry of Computer Software Technology Computer Software Association Shanghai, China Testing and Evaluating Shanghai, China [email protected] Shanghai, China [email protected] {lzy, jiangx}@ssc.stn.sh.cn Abstract—This paper studies the software scenario testing, emerged in recent years, few of them provide any which is commonly used in black-box testing. In the paper, the consideration for business workflow verification. workflow model based on task-driven, which is very common The research work on business scenario testing and in scenario testing, is analyzed. According to test business validation is less. As for the actual development of the model in scenario testing, the model is designed to application system, the every operation in business is corresponding test case suite. The test case suite that conforms designed and developed well. However, business processes to the scenario test can be obtained through test case testing and requirements verification are very important and generation and test item design. In the last part of the paper, necessary for software quality. The scenario testing satisfies framework of test case suite design is given to illustrate the software requirement through the test design and test effectiveness of the method. execution. Keywords-test case; software test; scenario testing; test suite. Scenario testing is to judge software logic correction according to data behavior in finite test data and is to analyze results with all the possible input test data.
    [Show full text]
  • Evaluating Testing with a Test Level Matrix
    FSW QA Testing Levels Definitions Copyright 2000 Freightliner LLC. All rights reserved. FSW QA Testing Levels Definitions 1. Overview This document is used to help determine the amount and quality of testing (or its scope) that is planned for or has been performed on a project. This analysis results in the testing effort being assigned to a particular Testing Level category. Categorizing the quality and thoroughness of the testing that has been performed is useful when analyzing the metrics for the project. For example if only minimum testing was performed, how come so many person-hours were spent testing? Or if the maximum amount of testing was performed, how come there are so many trouble calls coming into the help desk? 2. Testing Level Categories This section provides the basic definitions of the six categories of testing levels. The definitions of the categories are intentionally vague and high level. The Testing Level Matrix in the next section provides a more detailed definition of what testing tasks are typically performed in each category. The specific testing tasks assigned to each category are defined in a separate matrix from the basic category definitions so that the categories can easily be re-defined (for example because of QA policy changes or a particular project's scope - patch release versus new product development). If it is decided that a particular category of testing is required on a project, but a testing task defined for completion in that category is not performed, it will be noted in the Test Plan (if it exists) and in the Testing Summary Report.
    [Show full text]
  • Tips for Success
    Tips for Success EHR System Implementation Testing By this stage of your EHR system implementation, you have fully grasped the significant flexibility of your EHR system, and have devoted significant hours to making major set-up and configuration decisions to tailor the system to your specific needs and clinical practices. Most likely, you have spent many long hours and late nights designing new workflow processes, building templates, configuring tables and dictionaries, setting system triggers, designing interfaces, and building screen flow logic to make the system operate effectively within your practice. Now, it is absolutely critical to thoroughly test your “tailoring” to be sure the system and screens work as intended before moving forward with “live” system use. It is far easier to make changes to the system configuration while there are no patients and physicians sitting in the exam rooms growing impatient and frustrated. Testing (and more testing!) will help you be sure all your planning and hard work thus far pays off in a successful EHR “Go-Live”. The following outlines an effective, proven testing process for assuring your EHR system works effectively and as planned before initial “Go-Live”. 1. Assign and Dedicate the Right Testing Resources Effectively testing a system requires significant dedicated time and attention, and staff that have been sufficiently involved with planning the EHR workflows and processes, to fully assess the set up of the features and functions to support its intended use. Testing also requires extreme patience and attention to detail that are not necessarily skills all members of your practice staff possess.
    [Show full text]
  • Standard Glossary of Terms Used in Software Testing Version 3.0 Advanced Test Analyst Terms
    Standard Glossary of Terms used in Software Testing Version 3.0 Advanced Test Analyst Terms International Software Testing Qualifications Board Copyright Notice This document may be copied in its entirety, or extracts made, if the source is acknowledged. Copyright © International Software Testing Qualifications Board (hereinafter called ISTQB®). acceptance criteria Ref: IEEE 610 The exit criteria that a component or system must satisfy in order to be accepted by a user, customer, or other authorized entity. acceptance testing Ref: After IEEE 610 See Also: user acceptance testing Formal testing with respect to user needs, requirements, and business processes conducted to determine whether or not a system satisfies the acceptance criteria and to enable the user, customers or other authorized entity to determine whether or not to accept the system. accessibility testing Ref: Gerrard Testing to determine the ease by which users with disabilities can use a component or system. accuracy Ref: ISO 9126 See Also: functionality The capability of the software product to provide the right or agreed results or effects with the needed degree of precision. accuracy testing See Also: accuracy Testing to determine the accuracy of a software product. actor User or any other person or system that interacts with the test object in a specific way. actual result Synonyms: actual outcome The behavior produced/observed when a component or system is tested. adaptability Ref: ISO 9126 See Also: portability The capability of the software product to be adapted for different specified environments without applying actions or means other than those provided for this purpose for the software considered.
    [Show full text]
  • →Different Models(Waterfall,V Model,Spiral Etc…) →Maturity Models. → 1. Acceptance Testing: Formal Testing Conducted To
    different models(waterfall,v model,spiral etc…) maturity models. 1. Acceptance Testing: Formal testing conducted to determine whether or not a system satisfies its acceptance criteria and to enable the customer to determine whether or not to accept the system. It is usually performed by the customer. 2. Accessibility Testing: Type of testing which determines the usability of a product to the people having disabilities (deaf, blind, mentally disabled etc). The evaluation process is conducted by persons having disabilities. 3. Active Testing: Type of testing consisting in introducing test data and analyzing the execution results. It is usually conducted by the testing teams. 4. Agile Testing: Software testing practice that follows the principles of the agile manifesto, emphasizing testing from the perspective of customers who will utilize the system. It is usually performed by the QA teams. 5. Age Testing: Type of testing which evaluates a system's ability to perform in the future. The evaluation process is conducted by testing teams. 6. Ad-hoc Testing: Testing performed without planning and documentation - the tester tries to 'break' the system by randomly trying the system's functionality. It is performed by the testing teams. 7. Alpha Testing: Type of testing a software product or system conducted at the developer's site. Usually it is performed by the end user. 8. Assertion Testing: Type of testing consisting in verifying if the conditions confirm the product requirements. It is performed by the testing teams. 9. API Testing: Testing technique similar to unit testing in that it targets the code level. API Testing differs from unit testing in that it is typically a QA task and not a developer task.
    [Show full text]
  • The Nature of Exploratory Testing
    The Nature of Exploratory Testing by Cem Kaner, J.D., Ph.D. Professor of Software Engineering Florida Institute of Technology and James Bach Principal, Satisfice Inc. These notes are partially based on research that was supported by NSF Grant EIA-0113539 ITR/SY+PE: "Improving the Education of Software Testers." Any opinions, findings and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation. Kaner & Bach grant permission to make digital or hard copies of this work for personal or classroom use, including use in commercial courses, provided that (a) Copies are not made or distributed outside of classroom use for profit or commercial advantage, (b) Copies bear this notice and full citation on the front page, and if you distribute the work in portions, the notice and citation must appear on the first page of each portion. Abstracting with credit is permitted. The proper citation for this work is ”Exploratory & Risk-Based Testing (2004) www.testingeducation.org", (c) Each page that you use from this work must bear the notice "Copyright (c) Cem Kaner and James Bach", or if you modify the page, "Modified slide, originally from Cem Kaner and James Bach", and (d) If a substantial portion of a course that you teach is derived from these notes, advertisements of that course should include the statement, "Partially based on materials provided by Cem Kaner and James Bach." To copy otherwise, to republish or post on servers, or to distribute to lists requires prior specific permission and a fee.
    [Show full text]
  • What Is a Good Test Case? Cem Kaner, J.D., Ph.D
    What Is a Good Test Case? Cem Kaner, J.D., Ph.D. Florida Institute of Technology Department of Computer Sciences [email protected] STAR East, May 2003 This research was partially supported by NSF Grant EIA-0113539 ITR/SY+PE: "Improving the Education of Software Testers." Any opinions, findings and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation (NSF). Abstract Designing good test cases is a complex art. The complexity comes from three sources: Test cases help us discover information. Different types of tests are more effective for different classes of information. Test cases can be “good” in a variety of ways. No test case will be good in all of them. People tend to create test cases according to certain testing styles, such as domain testing or risk-based testing. Good domain tests are different from good risk-based tests. What’s a Test Case? Let’s start with the basics. What’s a test case? IEEE Standard 610 (1990) defines test case as follows: “(1) A set of test inputs, execution conditions, and expected results developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement. “(2) (IEEE Std 829-1983) Documentation specifying inputs, predicted results, and a set of execution conditions for a test item.” According to Ron Patton (2001, p. 65), “Test cases are the specific inputs that you’ll try and the procedures that you’ll follow when you test the software.” Boris Beizer (1995, p.
    [Show full text]
  • ISTQB Glossary of Testing Terms 2.3X
    Standard glossary of terms used in Software Testing Version 2.3 (dd. March 28th, 2014) Produced by the ‘Glossary Working Party’ International Software Testing Qualifications Board Editor : Erik van Veenendaal (Bonaire) Copyright Notice This document may be copied in its entirety, or extracts made, if the source is acknowledged. Copyright © 2014, International Software Testing Qualifications Board (hereinafter called ISTQB®). 1 Acknowledgements This document was produced by the Glossary working group of the International Software Testing Qualifications Board (ISTQB). The team thanks the national boards for their suggestions and input. At the time the Glossary version 2.3 was completed the Glossary working group had the following members (alphabetic order): Armin Beer, Armin Born, Mette Bruhn-Pedersen, Josie Crawford, Ernst Dőring, George Fialkovitz, Matthias Hamburg, Bernard Homes, Ian Howles, Ozgur Kisir, Gustavo Marquez- Soza, Judy McKay (Vice-Chair) Avi Ofer, Ana Paiva, Andres Petterson, Juha Pomppu, Meile Posthuma. Lucjan Stapp and Erik van Veenendaal (Chair) The document was formally released by the General Assembly of the ISTQB on March, 28th, 2014 2 Change History Version 2.3 d.d. 03-28-2014 This new version has been developed to support the Foundation Extention Agile Tester syllabus. In addition a number of change request have been implemented in version 2.3 of the ISTQB Glossary. New terms added: Terms changed; - build verification test - acceptance criteria - burndown chart - accuracy testing - BVT - agile manifesto - content
    [Show full text]
  • Testing, SEED Infotech’S Service Portfolio Encompasses the Entire Range of Solutions Required by the IT Industry
    The Journey of Thousand miles starts with a single step Take the Step Today SEED Infotech Ltd. is Pune’s leading Training, Consulting and Staffing Company, offering a wide array of solutions customized for a range of key verticals and horizontals in the IT industry. From customized corporate training in IT, Project Management and Soft-skills to Strategy Consulting for the implementation of the right tools for enterprise wide planning, software development and testing, SEED Infotech’s service portfolio encompasses the entire range of solutions required by the IT industry. We have 33+ branches all across India. 16+ years of Experience in Technology Training, Staffing and Consulting 600 dedicated and highly skilled IT Professional with 200+ in house Trainers 1,80,000+ Students and Professional trained so far 1,00,000+ Sq. ft. of Training Infrastructure Courses mapped with Industry Requirement State-of-the-art IT laboratories and communication set-up 33+ Training Location across India Strategic tie-ups with Global Technology leaders Short Term IT Courses Job Oriented Diploma Courses C, C++ NET Java/J2EE Oracle IBM SEED - Diploma in Software Testing Linux PERL PHP IT for 10th & 12th IBM Tivoli Storage Manager SCTS - SEED Certified Technology Specialist (Java / .NET Track) Hardware & Networking Courses Technical Writing SPIC - Software Professionals’ Incubation Center A+ N+ MCSA CCNA SCHANSA - Java / .NET - Software Testing - Hardware & Networking - Tivoli Admin English & Foreign Languages SEED Tutorails Spoken English Japanese Chinese German English Maths Science Sanskrit German French Maths & English Aptitude French Marathi Hindi Computer Science Personality Development SEED Infotech Ltd. 'Panchasheel', 42/16, Erandawana, SEED Infotech Lane, Off Karve Road, Pune - 411004.
    [Show full text]