Manual Testing Contents

Total Page：16

File Type：pdf, Size：1020Kb

Manual Testing Contents Day – 1 Chapter 1: Introduction to Software Testing Why is testing necessary? What is testing? Testing Terminologies Economics of Testing Role of Manual Tester Software Testing Principles Introduction to Software Testing Life CycleSTLC Chapter 2: Testing throughout the software life cycle What is Software Development Life Cycle? What is SRS, BRS and URS Various Software Development models Water Fall Model V - Model Iterative Life Cycles Agile Model Spiral Model Test Levels Component Testing Integration Testing System Testing Acceptance Testing Maintenance testing Chapter 3: Static Testing VS Dynamic Testing Difference between Static and Dynamic Testing What is review Reviews and the test process Review Process Testing Techniques used for Static Testing Testing Techniques used for Dynamic Testing Day – 2 Chapter 4: Test Design Techniques Test Case Template How to prepare Test Cases Test Scenarios What is Requirement Traceability Matrix Identifying test conditions and designing test cases Categories of test design techniques Specification-based or black-box techniques Boundary Value Analysis Decision Table Testing Equivalence Partitioning State Transition Testing Use Case Testing Structure-based or white-box techniques Decision Coverage Statement Coverage Experience-based techniques Error Guessing Exploratory Testing Chapter 5: Test Management Test Plan Template How to prepare Test Plan Test Plans Estimationand strategies Test progress monitoring and control Configuration Management Risk and Testing Day – 3 Chapter 6: Other Testing Types Sanity Testing Regression Testing Volume Testing Stress Testing Usability Testing Security Testing Performance Testing Configuration Testing Reliability Testing Recovery Testing Load/Stress Testing Accessibility Testing Lesson 7: Severity/Priority What is Severity and types of Severity What is Priority and types of Priority Lesson 8: Defect Management What is Bug/defect Bug/defect Life Cycle Introduction to Bug Reporting Bug Tracking Tools Lesson 9: Introduction to Automation Testing What is Automation Testing Need of Automation Manual vs Automation which is better Various Automation Testing Tools Lesson 10: Hands on Exercise .

Copy Link

Recommended publications

Integration Testing of Object-Oriented Software
POLITECNICO DI MILANO DOTTORATO DI RICERCA IN INGEGNERIA INFORMATICA E AUTOMATICA Integration Testing of Object-Oriented Software Ph.D. Thesis of: Alessandro Orso Advisor: Prof. Mauro Pezze` Tutor: Prof. Carlo Ghezzi Supervisor of the Ph.D. Program: Prof. Carlo Ghezzi XI ciclo To my family Acknowledgments Finding the right words and the right way for expressing acknowledgments is a difﬁ- cult task. I hope the following will not sound as a set of ritual formulas, since I mean every single word. First of all I wish to thank professor Mauro Pezze` , for his guidance, his support, and his patience during my work. I know that “taking care” of me has been a hard work, but he only has himself to blame for my starting a Ph.D. program. A very special thank to Professor Carlo Ghezzi for his teachings, for his willingness to help me, and for allowing me to restlessly “steal” books and journals from his ofﬁce. Now, I can bring them back (at least the one I remember...) Then, I wish to thank my family. I owe them a lot (and even if I don't show this very often; I know this very well). All my love goes to them. Special thanks are due to all my long time and not-so-long time friends. They are (stricty in alphabetical order): Alessandro “Pari” Parimbelli, Ambrogio “Bobo” Usuelli, Andrea “Maken” Machini, Antonio “the Awesome” Carzaniga, Dario “Pitone” Galbiati, Federico “Fede” Clonfero, Flavio “Spadone” Spada, Gianpaolo “the Red One” Cugola, Giovanni “Negroni” Denaro, Giovanni “Muscle Man” Vigna, Lorenzo “the Diver” Riva, Matteo “Prada” Pradella, Mattia “il Monga” Monga, Niels “l’e´ semper chi” Kierkegaard, Pierluigi “San Peter” Sanpietro, Sergio “Que viva Mex- ico” Silva.
[Show full text]
Empirical Evaluation of the Effectiveness and Reliability of Software Testing Adequacy Criteria and Reference Test Systems
Empirical Evaluation of the Effectiveness and Reliability of Software Testing Adequacy Criteria and Reference Test Systems Mark Jason Hadley PhD University of York Department of Computer Science September 2013 2 Abstract This PhD Thesis reports the results of experiments conducted to investigate the effectiveness and reliability of ‘adequacy criteria’ - criteria used by testers to determine when to stop testing. The research reported here is concerned with the empirical determination of the effectiveness and reliability of both tests sets that satisfy major general structural code coverage criteria and test sets crafted by experts for testing specific applications. We use automated test data generation and subset extraction techniques to generate multiple tests sets satisfying widely used coverage criteria (statement, branch and MC/DC coverage). The results show that confidence in the reliability of such criteria is misplaced. We also consider the fault-finding capabilities of three test suites created by the international community to serve to assure implementations of the Data Encryption Standard (a block cipher). We do this by means of mutation analysis. The results show that not all sets are mutation adequate but the test suites are generally highly effective. The block cipher implementations are also seen to be highly ‘testable’ (i.e. they do not mask faults). 3 Contents Abstract ............................................................................................................................ 3 Table of Tables ...............................................................................................................
[Show full text]
Standard Glossary of Terms Used in Software Testing Version
Standard Glossary of Terms used in Software Testing Version 3.2 Foundation 2018 - Release Candidate 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®). Foundation 2018 - Release Candidate Terms Page: 2 of 29 acceptance criteria Ref: ISO 24765 The 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 ISO 24765 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 Ref: After ISO 25010 The degree to which a component or system can be used by people with the widest range of characteristics and capabilities to achieve a specified goal in a specified context of use. accessibility testing Ref: Gerrard Testing to determine the ease by which users with disabilities can use a component or system. actual result Synonyms: actual outcome The behavior produced/observed when a component or system is tested. ad hoc reviewing Ref: After ISO 20246 A review technique carried out by independent reviewers informally, without a structured process. alpha testing Simulated or actual operational testing conducted in the developer's test environment, by roles outside the development organization. anomaly Ref: IEEE 1044 See Also: defect, error, fault, failure, incident, problem Any condition that deviates from expectation based on requirements specifications, design documents, user documents, standards, etc., or from someone's perception or experience.
[Show full text]
Using Static Analysis to Determine Where to Focus Dynamic Testing Effort
Using Static Analysis to Determine Where to Focus Dynamic Testing Effort Thomas J. Ostrand Elaine J. Weyuker Robert M. Bell AT&T Labs - Research AT&T Labs - Research AT&T Labs - Research 180 Park Avenue 180 Park Avenue 180 Park Avenue Florham Park, NJ 07932 Florham Park, NJ 07932 Florham Park, NJ 07932 [email protected] [email protected] [email protected] Abstract termine which files in the system are most likely to contain the largest numbers of faults that lead to failures and pri- We perform static analysis and develop a negative bino- oritize our testing effort accordingly. In that way we min- mial regression model to predict which files in a large soft- imize the cost of testing and maximize the effectiveness of ware system are most likely to contain the largest numbers the process. In order to do this, we have been investigat- of faults that manifest as failures in the next release, using ing how to use data residing in a combined version control information from all previous releases. This is then used to and change management system used during all stages of guide the dynamic testing process for software systems by development, testing, and field release, to improve dynamic suggesting that files identified as being likely to contain the testing. largest numbers of faults be subjected to particular scrutiny Preliminary work was reported in an earlier paper [10] during dynamic testing. In previous studies of a large in- which described a case study involving an industrial inven- ventory tracking system, we identified characteristics of the tory tracking system, developed over a three year period, files containing the largest numbers of faults and those with covering twelve quarterly releases.
[Show full text]
Introduction to Unit Testing
Introduction Unit Testing Google Test LAMMPS Introduction to Unit Testing Ryan Houlihan March 18, 2013 Ryan Houlihan Introduction to Unit Testing Introduction Software Development Unit Testing Traditional Testing Google Test Proper Testing LAMMPS Software Development Lifecycle Ryan Houlihan Introduction to Unit Testing Introduction Software Development Unit Testing Traditional Testing Google Test Proper Testing LAMMPS Traditional Testing Test the system as a whole Higher level of complexity Individual components are rarely tested Isolating errors is problematic Testing Strategies Print Statements Use of Debugger Test Scripts Ryan Houlihan Introduction to Unit Testing Introduction Software Development Unit Testing Traditional Testing Google Test Proper Testing LAMMPS Proper Testing 1 Unit Testing (Developers) Individual components (class or subsystem) 2 Integration Testing (Developers) Aggregates of subsystems 3 System Testing (Developers) Complete integrated system Evaluates system’s compliance with specified requirements 4 Acceptance Testing (Client) Evaluates system delivered by developers Ryan Houlihan Introduction to Unit Testing Introduction Software Development Unit Testing Traditional Testing Google Test Proper Testing LAMMPS Benefits Limits complexity of issues Many bugs and errors are eliminated during development, not afterwards. Easier to extend code in future Confirms added functionalities compliance with specified requirements Saves time in the development cycle Limits extra system testing and debugging Eliminates logical errors
[Show full text]
Coordinating Requirements Engineering and Software Testing
ENGINEERING AND SOFTWARE TESTING ENGINEERING AND SOFTWARE REQUIREMENTS COORDINATING ABSTRACT The development of large, software-intensive sys- This thesis contains four main contributions: (1) tems is a complex undertaking that is generally An in-depth study on REST alignment challeng- tackled by a divide and conquer strategy. Organi- es and practices encountered in industry. (2) A COORDINATING REQUIREMENTS zations face thereby the challenge of coordinating conceptual framework in the form of a taxonomy ENGINEERING AND SOFTWARE TESTING the resources which enable the individual aspects providing constructs that further our understan- of software development, commonly solved by ding of REST alignment. The taxonomy is ope- adopting a particular process model. The alignme- rationalized in an assessment framework, REST- nt between requirements engineering (RE) and bench (3), that was designed to be lightweight software testing (ST) activities is of particular in- and can be applied as a postmortem in closing terest as those two aspects are intrinsically con- development projects. (4) An extensive investi- nected: requirements are an expression of user/ gation into the potential of information retrieval customer needs while testing increases the likeli- techniques to improve test coverage, a common hood that those needs are actually satisfied. REST alignment challenge, resulting in a solution The work in this thesis is driven by empirical pro- prototype, risk-based testing supported by topic Michael Unterkalmsteiner blem identification, analysis and solution develop- models (RiTTM). ment towards two main objectives. The first is to REST-bench has been validated in five cases and develop an understanding of RE and ST alignme- has shown to be efficient and effective in identi- nt challenges and characteristics.
[Show full text]
Review Paper on Various Software Testing
Global Journal of Computer Science and Technology: C Software & Data Engineering Volume 19 Issue 2 Version 1.0 Year 2019 Type: Double Blind Peer Reviewed International Research Journal Publisher: Global Journals Online ISSN: 0975-4172 & Print ISSN: 0975-4350 Review Paper on Various Software Testing Techniques & Strategies By Nahid Anwar & Susmita Kar Bangladesh University of Business and Technology Abstract - Software testing is the process of running an application with the intent of finding software bugs (errors or other defects). Software applications demand has pushed the quality assurance of developed software towards new heights. It has been considered as the most critical stage of the software development life cycle. Testing can analyze the software item to identify the disparity between actual and prescribed conditions and to assess the characteristics of the software. Software testing leads to minimizing errors and cut down software costs. For this purpose, we discuss various software testing techniques and strategies. This paper aims to study diverse as well as improved software testing techniques for better quality assurance purposes. Keywords: testing techniques, testing tools, verification, validation, level of testing, debugging, software testing objectives, software testing principles, software testing strategies, debugging, testing methodologies, software testing life cycle. GJCST-C Classification: D.2.5 ReviewPaperonVariousSoftwareTestingTechniquesStrategies Strictly as per the compliance and regulations of: © 2019. Nahid Anwar & Susmita Kar. This is a research/review paper, distributed under the terms of the Creative Commons Attribution- Noncommercial 3.0 Unported License http://creativecommons.org/licenses/by-nc/3.0/), permitting all non-commercial use, distribution, and reproduction inany medium, provided the original work is properly cited.
[Show full text]
Manual Testing Material
Manual Testing Material Address: #104,Nandini Residency, Addagutta Society, Beside KPHB Police station lane JNTU X-Roads, HYD Manual Testing Manual Testing 1. Introduction to Software Testing 1.1 What is Software Testing “Software testing is a process of executing the application with the intent of finding the defects by comparing the output behavior of the application with expected behavior (requirement).” In other words it’s comparing the actual behavior of an application with expected behavior. 1.2 Why Software Testing Humans make mistakes all the time!! “Software testing is really required to point out the defects and errors that were made during the development phases”. We humans can’t identify our mistakes in a work done by us. We should get someone else to check our work because another person may identify the mistakes done by us. In the same way software developers may not identify the mismatches in a program or application implemented by them which can be identify by the another department called Software Test Engineer. 1.3 Benefits of Software Testing “Software testing helps in finalizing the software application against business requirements.” Software testing makes sure that the testing is being done properly and hence the system is ready for the customers to use. Below are few benefits of software testing. - Finding the defects before delivery - Gaines the confidence about quality - To Prevent defects - Ensure the requirements are delivered to client 1.4 What is Quality “Software quality is nothing but delivering a bug free application and delivered on time with all requirements.” Website:www.testingmasters.com Email:[email protected] Page # 1 Manual Testing ISO 8402-1986 standard defines quality as “the totality of features and characteristics of a product or service that bears its ability to satisfy stated or implied needs.” 1.5 What is defect “A defect is a deviation or mismatch from the requirements”.
[Show full text]
Testing a Software Product Line
Testing a Software Product Line John D. McGregor December 2001 TECHNICAL REPORT CMU/SEI-2001-TR-022 ESC-TR-2001-022 Pittsburgh, PA 15213-3890 Testing a Software Product Line CMU/SEI-2001-TR-022 ESC-TR-2001-022 John D. McGregor December 2001 Product Line Systems Program Unlimited distribution subject to the copyright. This report was prepared for the SEI Joint Program Office HQ ESC/DIB 5 Eglin Street Hanscom AFB, MA 01731-2116 The ideas and findings in this report should not be construed as an official DoD position. It is published in the interest of scientific and technical information exchange. FOR THE COMMANDER Norton L. Compton, Lt Col, USAF SEI Joint Program Office This work is sponsored by the U.S. Department of Defense. The Software Engineering Institute is a federally funded research and development center sponsored by the U.S. Department of Defense. Copyright 2001 by Carnegie Mellon University. NO WARRANTY THIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTITUTE MATERIAL IS FURNISHED ON AN “AS-IS” BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MATTER INCLUDING, BUT NOT LIMITED TO, WARRANTY OF FITNESS FOR PURPOSE OR MERCHANTABILITY, EXCLUSIVITY, OR RESULTS OBTAINED FROM USE OF THE MATERIAL. CARNEGIE MELLON UNIVERSITY DOES NOT MAKE ANY WARRANTY OF ANY KIND WITH RESPECT TO FREEDOM FROM PATENT, TRADEMARK, OR COPYRIGHT INFRINGEMENT. Use of any trademarks in this report is not intended in any way to infringe on the rights of the trademark holder. Internal use. Permission to reproduce this document and to prepare derivative works from this document for internal use is granted, provided the copyright and “No Warranty” statements are included with all reproductions and derivative works.
[Show full text]
OWASP Testing Guide
1 Testing Guide 4.0 Project Leaders: Matteo Meucci and Andrew Muller Creative Commons (CC) Attribution Share-Alike Free version at http://www.owasp.org 2 THE ICONS BELOW REPRESENT WHAT YOU ARE FREE: OTHER VERSIONS ARE AVAILABLE IN PRINT FOR THIS BOOK TITLE. To Share - to copy, distribute and ALPHA: “Alpha Quality” book content is a transmit the work working draft. Content is very rough and in development until the next level of publishing. To Remix - to adapt the work BETA: “Beta Quality” book content is the next highest level. Content is still in development UNDER THE FOLLOWING CONDITIONS: until the next publishing. RELEASE: “Release Quality” book content Attribution. You must attribute the work is the highest level of quality in a book title’s in the manner specified by the author or lifecycle, and is a final product. licensor (but not in any way that suggests that they endorse you or your use of the work). Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under the same, similar or a compatible license. ALPHA BETA RELEASE The Open Web Application Security Project (OWASP) is a worldwide free and open com- munity focused on improving the security of application software. Our mission is to make application security “visible”, so that people and organizations can make informed decisions about application security risks. Every one is free to participate in OWASP and all of our materials are available under a free and open software license. The OWASP Foundation is a 501c3 not-for-profit charitable organization that ensures the ongoing availability and support for our work.
[Show full text]
Investigation of Manual and Automation Testing Using Assorted Approaches
International Journal of Scientific Research in _______________________________ Research Paper . Computer Science and Engineering Vol.5, Issue.2, pp.81-87, April (2017) E-ISSN: 2320-7639 Investigation of Manual and Automation Testing using Assorted Approaches Shruti Malve1* and Pradeep Sharma2 1Dept. of Computer Science, Govt. Holkar Science (Autonomous) College, Indore, India 2Dept. of Computer Science, Govt. Holkar Science (Autonomous) College, Indore, India Corresponding Author: [email protected] Available online at: www.isroset.org Received 15th Mar 2017, Revised 29th Mar 2017, Accepted 25th Apr 2017, Online 30th Apr 2017 Abstract- Testing means “revealing a person's capabilities by putting them under strain; challenging”. Software testing exist a vast domain, but it may be classify into two way: manual testing and automated testing. In manual testing, test cases are executed (run) manually without any help from tools/scripts, but with automated testing, test cases are executed (run) with the help of tools, scripts, and software. Software testing is expensive, labor intensive and consume more time in a software development life cycle. There was forever a need in software testing to decrease the testing time. The type of testing (manual or automated) depends on various factors, adding project need, budget, timeline, expertise, and suitability. Three fundamental factors of any project are of course time, cost, and quality – the objective of any successful project is to diminish the cost and time required to complete it successfully while maintaining quality output. When it comes to testing, one type may accomplish this goal better than the other. This paper presents the concept of automation and manual testing and problem with manual testing and benefit of automatic testing.
[Show full text]
Introduction to Software Testing
Introduction to Software Testing Instructor : Ali Sharifara, PhD CSE 4321/5321 Summer 2017 1 Agenda • Grader Info • Quick Review • Introduction to Software Testing • Input Space Partitioning 2 Outline • Introduction • Basic Concepts • The Testing Process • Types of Testing • Testing Philosophy • Summary 3 Introduction What is software testing ? Software testing is a check activity to validate whether the actual results matches with expected results and to ensure that the software system is bug free. Why it is needed ? – Field validation issues (e.g. check date of birth, or age, etc.) – Sites responsiveness under specific load (e.g. during a registration …) – Payment related issues (e.g. payment gateways) – Security issues (payment methods) – Verifying store policies and customer support (return policy, etc.) – Lack of device and browser compatibility (different browsers.) – etc. Lack of testing may lead to – Loss of money – Loss of time – Loss of business reputation 4 SQA, SQC, and Testing • Software Quality Assurance (SQA) – Is error preventive & verification activity. – SQA role is to observe that documented standards, processes, and procedures are followed as enforced by development • Software Quality Control (SQC) – is defect detection and validation activity. – SQC role (usually testers) is to validate the quality of a system and to check whether this application adheres the defined quality standards or not. • Testing – It includes activities that ensure that identification of bugs/error/defects in a software 5 Software Development Life Cycle • Software Development Life Cycle (SDLC) – A series of steps, or phases, that provides a model for the development and lifecycle management of an application or software • SDLC Steps SDLC methods – Requirement Analysis 1.
[Show full text]