1 Analyzed Software Testing Techniques ~ Black-Box

Total Page:16

File Type:pdf, Size:1020Kb

1 Analyzed Software Testing Techniques ~ Black-Box 1 ANALYZED SOFTWARE TESTING TECHNIQUES ~ BLACK-BOX TESTING, WHITE-BOX TESTING, GRAYBOX-TESTING COSC 5370 - ADVANCED SOFTWARE ENGINEERING TEXAS A&M UNIVERSITY – CORPUS CHRISTI SPRING 2014 BY MERT EVREN 2 Abstract ~ Testing is an important phase in software engineering Software testing methods are used for examination, verification and validation of the source code of a program. These methods are applied to software applications and their components to uncover hidden errors. Software testing includes experimentally and scientifically inspecting the correctness of the application. Software testing determines the applications quality by evaluating the capability of the application. The entire testing procedure should be well-structured. In this paper, three testing methodologies; black-box testing, white- box testing, and gray-box testing, are analyzed in detail. The remainder of this paper is structured as follows; section 2 describes black-box testing, white-box testing, and gray-box testing. Different testing techniques of each method has shown. These testing methods are analyzed by providing pros and cons of each. Section 3 presents possible improvement on testing methods. Lastly, section 4 concludes the paper. 3 1. INTRODUCTION Testing is an important phase in software engineering. “To develop high-quality software, it is essential to use software testing methods.” [1] Software testing is defined “as a process of accessing the functionality and correctness of a software through analysis.” [4] Software testing methods are used for examination, verification and validation of the source code of a program. These methods are applied to software applications and their components to uncover hidden errors. Software testing includes experimentally and scientifically inspecting the correctness of the application. Software testing determines the applications quality by evaluating the capability of the application. The entire testing procedure should be well-structured. “Testing process must balance the requirements, technical limitation and user expectation.” [7] Testing cost changes depends on the application and the type of test applied, however not testing the application can be even cost more. Testing is done in every stage of software life cycle. “Testing ensures that what you get in the end is what you wanted to build.” [7] In this paper, three testing methodologies; black-box testing, white-box testing, and gray-box testing, are analyzed in detail. The remainder of this paper is structured as follows; section 2 describes black-box testing, white-box testing, and gray-box testing. Different testing techniques of each method has shown. These testing methods are analyzed by providing pros and cons of each. Section 3 presents possible improvement on testing methods. Lastly, section 4 concludes the paper. 2. TESTING METHODS 2.1. BLACK-BOX TESTING Black box testing, sometimes named functional testing or behavioral testing, defined as “is a software testing techniques in which functionality of the software under test (SUT) is tested without looking at the internal code structure, implementation details and knowledge of internal paths of the software.” [2], mainly concentrates on testing whether or not the code does what it is 4 supposed to do developed from its functional requirements. Black box testing develops test cases by using the specifications of the program and it is done by using the output of the user interface as would an end-user. Black-box testing is not concerned with the process software takes to provide particular output, it is concerned with the output that results from the input. 2.1.1. BLACK-BOX TESTING TECHNIQUES Figure-1 - Black-Box Testing Techniques [5] There are many black-box testing techniques exists, as shown in Figure-1. Following are some black-box testing techniques. 2.1.1 EQUIVALENCE CLASS PARTITIONING This testing technique divides input values of a program unit into valid and invalid partitions where test cases derived from. 5 2.1.2 BOUNDARY VALUE ANALYSIS Boundary value analysis determines the boundaries of input values which includes error values and valid values. 2.1.3 FUZZY TESTING Fuzzy testing is used to discover implementation bugs by using “malformed / semi- malformed data injection in an automated or semi-automated fashion. Fuzzing is also used to test for security problems in software.” [2] 2.1.2. PROS Very efficient and suited for testing large code segments. Simply focuses on if valid and invalid inputs provide correct outputs. Black-box testing is quite easy, advantaging tester’s usage with no coding skills or the knowledge of software implementation. Once the specifications are done, test cases can be designed. Tester are only concerned with GUI, internal paths of the program are not required to be analyzed. “The test cases can show presence or absence of classes of errors.” [7] 2.1.3. CONS Since black-box testing is based on GUI, it makes it hard for maintaining script when the user interface constantly changes. Because black-box testing doesn’t look into the internal code, the program can never be fully tested. “Blind Coverage: cannot control targeting code segments or paths which may be more error prone than others.” [2] 6 “Only small numbers of possible input can actually be tested.”[7] The test may be already executed on the program by its programmer which causes redundant testing. 2.2. WHITE-BOX TESTING White-box testing digs deep into the internal code of software. [2] Describes why this testing method named white-box “This method is named so because the software program, in the eyes of the tester, is like a white/transparent box; inside which one clearly sees.” White box testing investigates the implementation of the components in the source code, in another word white-box testing allows testers to see what is happening inside of the software. “White box testing is considered as a security testing method that can be used to validate whether code implementation follows intended design, to validate implemented security functionality, and to uncover exploitable vulnerabilities.” [7] White box testing provides full understanding of the internal mechanism of the application. “In white box testing it is necessary for a tester to have full knowledge of source code” [4] White-box testing is very efficient on revealing errors. “Exhaustive correctness checking is performed, all code paths are executed to ensure quality software outcome with reduced defect rate.” [5] 2.2.1. WHITE-BOX TESTING TECHNIQUES There are many existing test techniques for white-box testing as show in Figure-2. Here are the some of the white-box testing techniques analyzed. 2.2.1.1. CONTROL FLOW TESTING Control-flow testing is an efficient techniques for most of the software. “It is a structural testing strategy that uses the program control flow as a model control flow and favors more but simpler paths over fewer but complicated path.”[4] 7 2.2.1.2. BASIC PATH TESTING Basic path testing confirms that each independent path in the application source code is taken in a predetermined order. “It allows the test case designer to produce a logical complexity measure of procedural design and use this measure as an approach for outlining a basic set of execution path” [2] 2.2.1.3. DATA FLOW TESTING Data flow testing focuses on how data communicates within the system. It is used on modules with nested if and loop statements to detect variable that are unused or not initialized. 2.2.1.4. CONDITION TESTING Condition testing concentrates on the logical conditions of the program methods. Figure-2 – White-Box Testing Techniques 8 2.2.2. PROS Allows internal code to be fully tested where objects are able to be identified programmatically. “All independent paths in a module will be exercised at least once.” [7] Looking deep into implementation in detail allows programming errors to be easily detected. Behavior of software modules can be uncovered since testing involves accessing to source code. 2.2.3. CONS “It is nearly impossible to look into every bit of code to find out hidden errors, which may create problems, resulting in failure of the application.”[7] Testers have to be familiar with testing tools. Testers needs to be skilled in coding languages. Because of these requirements, it becomes difficult to scale testers. White-box testing uses test scripts. Implementation of these test scripts are tied to the source code of the application. Maintenance becomes very hard when any change made to the code. 2.3. GRAY-BOX TESTING Gray-box testing, also called as translucent testing, is combination of white-box testing and black-box testing. Gray-box testing is defined as, “a technique of testing the application with limited knowledge of the internal working of an application and also has the knowledge of fundamental aspects of the system” [4] Documentation of the program needs to be provided to testers in order to execute the tests. “The aim of this testing is to search for the defects if any due to improper structure or improper usage of applications.” [2] “Grey box testing technique will 9 increase the testing coverage by allowing us to focus on all the layers of any complex system through the combination of all existing white box and black box testing.” [4] Figure 3 – Representation of Gray-box Testing [4] 2.3.1. GRAY-BOX TESTING TECHNIQUES 2.3.1.1. MATRIX TESTING Status report of the application is generated which includes the relationship between the test requirements and the test cases. This report allows testers to analyze which requirements are included in which test cases. 2.3.1.2. REGRESSION TESTING This test is applied after new changes are made, such as functional improvement, to the source code of the application “Its purpose is to determine if the change has regressed other aspects of the program.” [2] Regression testing is a regular step of the software implementation procedure.
Recommended publications
  • 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]
  • Comparison of GUI Testing Tools for Android Applications
    Comparison of GUI testing tools for Android applications University of Oulu Department of Information Processing Science Master’s Thesis Tomi Lämsä Date 22.5.2017 2 Abstract Test automation is an intriguing area of software engineering, especially in Android development. This is since Android applications must be able to run in many different permutations of operating system versions and hardware choices. Comparison of different tools for automated UI testing of Android applications is done in this thesis. In a literature review several different tools available and their popularity is researched and the structure of the most popular tools is looked at. The two tools identified to be the most popular are Appium and Espresso. In an empirical study the two tools along with Robotium, UiAutomator and Tau are compared against each other in test execution speed, maintainability of the test code, reliability of the test tools and in general issues. An empirical study was carried out by selecting three Android applications for which an identical suite of tests was developed with each tool. The test suites were then run and the execution speed and reliability was analysed based on these results. The test code written is also analysed for maintainability by calculating the lines of code and the number of method calls needed to handle asynchrony related to UI updates. The issues faced by the test developer with the different tools are also analysed. This thesis aims to help industry users of these kinds of applications in two ways. First, it could be used as a source on what tools are over all available for UI testing of Android applications.
    [Show full text]
  • Evaluation Approaches in Software Testing Ayaz Farooq, Reiner R
    Nr.: FIN-05-2008 Evaluation Approaches in Software Testing Ayaz Farooq, Reiner R. Dumke Arbeitsgruppe Softwaretechnik Fakultät für Informatik Otto-von-Guericke-Universität Magdeburg Impressum (§ 10 MDStV): Herausgeber: Otto-von-Guericke-Universität Magdeburg Fakultät für Informatik Der Dekan Verantwortlich für diese Ausgabe: Otto-von-Guericke-Universität Magdeburg Fakultät für Informatik Reiner Dumke Postfach 4120 39016 Magdeburg E-Mail: [email protected] http://www.cs.uni-magdeburg.de/Preprints.html Auflage: 81 Redaktionsschluss: Juli 2008 Herstellung: Dezernat Allgemeine Angelegenheiten, Sachgebiet Reproduktion Bezug: Universitätsbibliothek/Hochschulschriften- und Tauschstelle Otto-von-Guericke-University of Magdeburg Faculty of Computer Science Institute for Distributed Systems Software Engineering Group Evaluation Approaches in Software Testing Authors: Ayaz Farooq Reiner R. Dumke University of Magdeburg Faculty of Computer Science P.O. Box 4120, 39016 Magdeburg Germany Farooq, Ayaz Dumke, Reiner R. Evaluation Approaches in Software Testing Technical Report Otto-von-Guericke-University of Magdeburg 2008. Contents i Contents 1 Introduction 1 1.1 Evaluation Defined . 2 1.2 Evaluation in Software Engineering . 2 1.3 Evaluation in Software Testing . 3 1.4 Structure of the Report . 5 2 Test Processes: Basics & Maturities 7 2.1 Test Process Fundamentals . 7 2.1.1 Test Process Contexts . 9 2.1.2 Research over Test Process . 10 2.2 Test Process Definition & Modeling . 11 2.2.1 Generic Test Process Descriptions . 11 2.2.1.1 Test Management Approach-TMap . 13 2.2.1.2 Drabick’s Formal Testing Process . 13 2.2.1.3 Test Driven Development . 15 2.2.1.4 Independent Verification & Validation . 17 2.2.2 Domain Specific Test Processes .
    [Show full text]
  • Exploring Languages with Interpreters and Functional Programming Chapter 11
    Exploring Languages with Interpreters and Functional Programming Chapter 11 H. Conrad Cunningham 24 January 2019 Contents 11 Software Testing Concepts 2 11.1 Chapter Introduction . .2 11.2 Software Requirements Specification . .2 11.3 What is Software Testing? . .3 11.4 Goals of Testing . .3 11.5 Dimensions of Testing . .3 11.5.1 Testing levels . .4 11.5.2 Testing methods . .6 11.5.2.1 Black-box testing . .6 11.5.2.2 White-box testing . .8 11.5.2.3 Gray-box testing . .9 11.5.2.4 Ad hoc testing . .9 11.5.3 Testing types . .9 11.5.4 Combining levels, methods, and types . 10 11.6 Aside: Test-Driven Development . 10 11.7 Principles for Test Automation . 12 11.8 What Next? . 15 11.9 Exercises . 15 11.10Acknowledgements . 15 11.11References . 16 11.12Terms and Concepts . 17 Copyright (C) 2018, H. Conrad Cunningham Professor of Computer and Information Science University of Mississippi 211 Weir Hall P.O. Box 1848 University, MS 38677 1 (662) 915-5358 Browser Advisory: The HTML version of this textbook requires a browser that supports the display of MathML. A good choice as of October 2018 is a recent version of Firefox from Mozilla. 2 11 Software Testing Concepts 11.1 Chapter Introduction The goal of this chapter is to survey the important concepts, terminology, and techniques of software testing in general. The next chapter illustrates these techniques by manually constructing test scripts for Haskell functions and modules. 11.2 Software Requirements Specification The purpose of a software development project is to meet particular needs and expectations of the project’s stakeholders.
    [Show full text]
  • Software Testing: Essential Phase of SDLC and a Comparative Study Of
    International Journal of System and Software Engineering Volume 5 Issue 2, December 2017 ISSN.: 2321-6107 Software Testing: Essential Phase of SDLC and a Comparative Study of Software Testing Techniques Sushma Malik Assistant Professor, Institute of Innovation in Technology and Management, Janak Puri, New Delhi, India. Email: [email protected] Abstract: Software Development Life-Cycle (SDLC) follows In the software development process, the problem (Software) the different activities that are used in the development of a can be dividing in the following activities [3]: software product. SDLC is also called the software process ∑ Understanding the problem and it is the lifeline of any Software Development Model. ∑ Decide a plan for the solution Software Processes decide the survival of a particular software development model in the market as well as in ∑ Coding for the designed solution software organization and Software testing is a process of ∑ Testing the definite program finding software bugs while executing a program so that we get the zero defect software. The main objective of software These activities may be very complex for large systems. So, testing is to evaluating the competence and usability of a each of the activity has to be broken into smaller sub-activities software. Software testing is an important part of the SDLC or steps. These steps are then handled effectively to produce a because through software testing getting the quality of the software project or system. The basic steps involved in software software. Lots of advancements have been done through project development are: various verification techniques, but still we need software to 1) Requirement Analysis and Specification: The goal of be fully tested before handed to the customer.
    [Show full text]
  • Software Testing Training Module
    MAST MARKET ALIGNED SKILLS TRAINING SOFTWARE TESTING TRAINING MODULE In partnership with Supported by: INDIA: 1003-1005,DLF City Court, MG Road, Gurgaon 122002 Tel (91) 124 4551850 Fax (91) 124 4551888 NEW YORK: 216 E.45th Street, 7th Floor, New York, NY 10017 www.aif.org SOFTWARE TESTING TRAINING MODULE About the American India Foundation The American India Foundation is committed to catalyzing social and economic change in India, andbuilding a lasting bridge between the United States and India through high impact interventions ineducation, livelihoods, public health, and leadership development. Working closely with localcommunities, AIF partners with NGOs to develop and test innovative solutions and withgovernments to create and scale sustainable impact. Founded in 2001 at the initiative of PresidentBill Clinton following a suggestion from Indian Prime Minister Vajpayee, AIF has impacted the lives of 4.6million of India’s poor. Learn more at www.AIF.org About the Market Aligned Skills Training (MAST) program Market Aligned Skills Training (MAST) provides unemployed young people with a comprehensive skillstraining that equips them with the knowledge and skills needed to secure employment and succeed on thejob. MAST not only meets the growing demands of the diversifying local industries across the country, itharnesses India's youth population to become powerful engines of the economy. AIF Team: Hanumant Rawat, Aamir Aijaz & Rowena Kay Mascarenhas American India Foundation 10th Floor, DLF City Court, MG Road, Near Sikanderpur Metro Station, Gurgaon 122002 216 E. 45th Street, 7th Floor New York, NY 10017 530 Lytton Avenue, Palo Alto, CA 9430 This document is created for the use of underprivileged youth under American India Foundation’s Market Aligned Skills Training (MAST) Program.
    [Show full text]
  • Model-Based Verification for SIMULINK Design
    Minnesota State University, Mankato Cornerstone: A Collection of Scholarly and Creative Works for Minnesota State University, Mankato All Graduate Theses, Dissertations, and Other Graduate Theses, Dissertations, and Other Capstone Projects Capstone Projects 2015 Model-Based Verification for SIMULINK Design Victor Oke Minnesota State University - Mankato Follow this and additional works at: https://cornerstone.lib.mnsu.edu/etds Part of the Electrical and Computer Engineering Commons Recommended Citation Oke, V. (2015). Model-Based Verification for SIMULINK Design [Master’s thesis, Minnesota State University, Mankato]. Cornerstone: A Collection of Scholarly and Creative Works for Minnesota State University, Mankato. https://cornerstone.lib.mnsu.edu/etds/517/ This Thesis is brought to you for free and open access by the Graduate Theses, Dissertations, and Other Capstone Projects at Cornerstone: A Collection of Scholarly and Creative Works for Minnesota State University, Mankato. It has been accepted for inclusion in All Graduate Theses, Dissertations, and Other Capstone Projects by an authorized administrator of Cornerstone: A Collection of Scholarly and Creative Works for Minnesota State University, Mankato. Model-Based Verification for SIMULINK Design By Victor Oke Master’s Thesis submitted in partial fulfillment of the requirements for the degree of Masters of Science in Engineering. Department of Electrical and Computer Engineering and Technology Minnesota State University, Mankato Mankato, Minnesota December 2015 Advisor: Dr. Nannan
    [Show full text]
  • Software Testing: Way to Develop Quality Software Product 1Dipti Pawade, 2Harshada Sonkamble, 3Pranchal Chaudhari, 4Shubhangi Rathod 1,2,3Dept
    ISSN : 0976-8491 (Online) | ISSN : 2229-4333 (Print) IJCST VOL . 4, Iss UE SPL - 1, JAN - MAR C H 2013 Software Testing: Way to Develop Quality Software Product 1Dipti Pawade, 2Harshada Sonkamble, 3Pranchal Chaudhari, 4Shubhangi Rathod 1,2,3Dept. of I T, K. J. Somaiya College of Engineering, Mumbai, India 4Dept. of IT, P. I. I. T. M. S. R., Navi Mumbai, India Abstract reaction to the input. The testing is a process of comparing the Software testing is one of the most important phase of software behaviour of the software against oracles principles by which one development life cycle. No one can underestimate the importance can recognize a problem. The good practice is to test software of software testing process on software quality assurance. as early as it has been written. The testing concept is evolved Organization pays 40% of its efforts on testing process. A powerful with time. Table 1 illustrate the concept evolution of testing [1]. testing technique results in reduced software development cost Software testing life cycle comprises of the different phases [2] and time and improved performance. That is why choosing an mentioned in Table 2. appropriate testing technique is very important. In this paper we have discussed various testing approaches and methods, their Table 2: Software Testing Life Cycle peculiarities and finally discussed functional and non-functional Phase Activity testing. Phase I: Software requirements/design is Requirements/ reviewed in detail and basic idea of Keywords Design Review what needs to be tested is derived. Testing Evolution, Software Testing Life Cycle, Testing Approach, Testing Technique, Functional Testing, Non-functional Testing Phase II: Detailed test plan is derived.
    [Show full text]
  • Orthogonal Array Application for Optimized Software Testing
    WSEAS TRANSACTIONS on COMPUTERS Ljubomir Lazic and Nikos Mastorakis Orthogonal Array application for optimal combination of software defect detection techniques choices LJUBOMIR LAZICa, NIKOS MASTORAKISb aTechnical Faculty, University of Novi Pazar Vuka Karadžića bb, 36300 Novi Pazar, SERBIA [email protected] http://www.np.ac.yu bMilitary Institutions of University Education, Hellenic Naval Academy Terma Hatzikyriakou, 18539, Piraeu, Greece [email protected] Abstract: - In this paper, we consider a problem that arises in black box testing: generating small test suites (i.e., sets of test cases) where the combinations that have to be covered are specified by input-output parameter relationships of a software system. That is, we only consider combinations of input parameters that affect an output parameter, and we do not assume that the input parameters have the same number of values. To solve this problem, we propose interaction testing, particularly an Orthogonal Array Testing Strategy (OATS) as a systematic, statistical way of testing pair-wise interactions. In software testing process (STP), it provides a natural mechanism for testing systems to be deployed on a variety of hardware and software configurations. The combinatorial approach to software testing uses models to generate a minimal number of test inputs so that selected combinations of input values are covered. The most common coverage criteria are two-way or pairwise coverage of value combinations, though for higher confidence three-way or higher coverage may be required. This paper presents some examples of software-system test requirements and corresponding models for applying the combinatorial approach to those test requirements. The method bridges contributions from mathematics, design of experiments, software test, and algorithms for application to usability testing.
    [Show full text]
  • Time Gray-‐Box Testing with DT
    Real-Time Gray-Box Testing with DT-10 Trinity Technologies About Gray-Box Testing: In 1999, Andre C. Coulter of Lockheed Martin Missiles and Fire Control - Orlando, published a paper on Gray-Box Testing, “Gray-Box Testing Methodology”, which repositioned the testing methodology that combines both White-Box Testing and Black-Box testing. In the following year, using the previous Gray-Box Testing knowledge as basis, Lockheed Martin has further perfected the Gray-Box Testing methodology by describing how to perform Gray-Box Testing in a real-time embedded device in a real environment [reference: Graybox Software Testing in the Real World in Real-Time]. The Gray-Box Testing methodology not only uses the coverage information to validate software’s correctness and test completeness, but also, uses the performance analysis to verify if the embedded device’s performance specs satisfy the real-time system’s requirement. We all know that from the system’s perspective, Black-Box testing scenarios are derived from system’s requirement documentations and design documentations, to see if the functionalities satisfy the requirement of the system. Because System-level testing is on a higher level and does not involve source code, testers only need to understand the require documentations and design and execute the testing scenario base on these documentations. This is simple, but the testing is not deep enough, thus unable to identify issues that are hard to find and pinpoint. White-Box Testing, also known as Unit Testing, normally is written by developer to perform testing on the code he or she has written.
    [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]
  • Download Mobile Testing Tutorial (PDF Version)
    Mobile Testing About the Tutorial This tutorial will help the audience to learn the different aspect of the up-trending mobile device testing as well as mobile application testing. You will get familiar with many useful tools for black-box and white-box testing of a mobile application. This tutorial also provides a deep insight on mobile device automation testing. Using this tutorial, you can enable yourself for up-to-date test planning for mobile device and mobile device application testing. In addition, you shall be able to automate basic test scripts for mobile device application testing. Audience If you are a quality assurance engineer having interest in mobile device testing as well as mobile device application testing, this tutorial will turn out to be a helping guide. Prerequisites A reader should know basic software testing concepts such as test planning, black-box testing tricks, etc. In addition, it will help a great deal if the reader is familiar with any scripting languages, for example, JavaScript. Disclaimer & Copyright © Copyright 2016 by Tutorials Point (I) Pvt. Ltd. All the contents and graphics published in this e-book are the property of Tutorials Point (I) Pvt. Ltd. The user of this e-book can download, read, print, or keep it for his/her personal use. However, it is strictly prohibited to reuse, retain, print, copy, distribute, or republish whole or the part of this e-book in any manner for the commercial purpose without written consent of the publisher. We strive to produce and update the contents and tutorials of our website accurately and precisely, however, the contents may contain some inaccuracies or errors.
    [Show full text]