DOCSLIB.ORG

Comparison of Software Testing Review Black Box and White Box and Gray

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Comparison of Software Testing Review Black Box and White Box and Gray International Journal of Mathematics and Computer Sciences (IJMCS) ISSN: 2305-7661 Volume.43 2015 www.scholarism.net Comparison of software testing review Black Box and White Box and Gray Box 1,* Mahdi babaeian 2 Vajihe ghasemiyan 3 Reza Nourmandi-pour 1,*Department of Computer, Science and Research branch, Islamic Azad University, Sirjan, Iran [email protected] 2Department of Computer, Science and Research branch, Islamic Azad University, Sirjan, Iran [email protected] 3Department of Computer, Sirjan branch, Islamic Azad University, Sirjan, Iran [email protected] Abstract According to the basic needs of the growing market for software and community software products, process, software testing, both in terms of quality and reliability are important. The problem with most software testing is too low. In this article, we define the testing software and its goals and then testing different software debugging software to fully explain. After a full explanation cycle software testing, test methods include: Black Box and White Box and Gray Box provided and the differences and advantages and disadvantages of the three methods evaluated. And better methods have identified three methods of software testing. Keywords- software testing, software testing cycle, Black Box, White Box, Gray Box 1442 International Journal of Mathematics and Computer Sciences (IJMCS) ISSN: 2305-7661 Volume.43 2015 www.scholarism.net Introduction As we see software sales market gradually grows, so quality and product reliability is one of the most fundamental issues is the software production process. Software testing process that measures the quality of computer software. Software testing include the implementation of a program aimed at finding software bugs, but is not limited to it. Quality is not absolute, Quality is not absolute, but relative to different people. With this picture, testing can never completely prove the correctness of custom computer software. An important point is that software testing, must be considered from different points of view of software quality assurance, which is associated with all areas of the business process, not just the areas of testing. To check the quality of the testing criteria or metrics exist; based on the decisions about the status of the application under test, the time for release of the software, and so did the risk of the release of the software. Tests are very different and varied metrics and far more numerous and indefinite. To select the appropriate application-specific metrics that we have information on different metrics and use them. In 2010, there was another problem in the Tokyo stock market and because of problems with system operation was suspended for 12 days. Reported reason for the error, server did not initialize memory. Could not be initialized memory under certain conditions [1]. So it is clear that to deliver the right product and reliable to the user, the application must be fully tested. All the errors and problems that cause the application to be useless, should be identified and resolved. Software Testing The purpose of software testing is knowing whether or not the software is correct. With this view, product testing software, like other products. But unlike other tangible goods, software has different problems. Because users do not see the software application problems, unless these problems are apparent under certain conditions. When we work with a tangible product, Possible before the problem, mark it will receive. In other words, as long as certain conditions are not tested, Software just works normally. In general it can be said, the problems in the application because of the weakness of their test. Due to the increasing complexity and proliferation of applications, the importance of software testing gradually increase. So testing problems also gradually increased. The purpose of software testing a. The increase in software quality b. Examine the system to meet the needs and Reliability c. identify weaknesses, errors and wrong application [5]. difference test software debugging software Because most people do not know the difference between software testing and debugging is possible in the early days of programming, control or failure of our program [2]. Because these little bugs called Bug and to try to fix the bugs also Debugging (debug ) it is said. Because software testing related to debugging. Therefore, these two should be separated. Difference between the two in Table 1 below. Although both aim to improve the quality of software, but debugging, software bugs cater but the test detects software vulnerabilities which includes aspects of the system there is software that works [4]. In other words, debug, profile satisfies the predetermined while the test detects a condition that makes it difficult for users. Problem identified by the debugging, it can bring the logic expected in the original plan are not met or the content of the application forms has occurred. On the other hand, system errors that are identified by software testing, Risks for users and software The software should be designed and implemented to prevent these errors [3]. 1443 International Journal of Mathematics and Computer Sciences (IJMCS) ISSN: 2305-7661 Volume.43 2015 www.scholarism.net If the programmer is used as a software tester bug likely will not be detected when available. Cycle software testing Although the software testing process in different organizations, however, software testing has the following cycle: a. Analysis of needs: needs analysis phase of the life cycle of software testing should be performed. b. Design Analysis: In this phase, testers and designers work to determine which part of the design test and which parameters should be used when testing. c. Test design: In this stage testing strategy becomes clear. d. Run the test: the test run and test their software providers and any errors are reported to the developer. e. Test Report: After the testing was completed, recent test results in the form of a report that and determines whether software is usable or not [6]. Software testing methods In general, we discussed four ways in software testing. These include: Testing Black Box and White Box testing and Gray Box testing and TDD. And then the main difference between Black Box and White Box test methods cover and at the end of the advantages and disadvantages of the four methods of software testing and review. V-I-testing Black Box Black-box testing is based on the assumption that the test is not aware of the contents and software algorithms. This test is done by a team of testers or end users. It is sometimes also called functional test, a test that has no internal mechanism of a system or a significant tool and only on the output generated based on the input selected and focused terms of performance [7]. Figure 1 shows the Black Box testing scheme. program input output output Figure 1: Scheme Testing Black Box [7] V.I.I-test techniques Black Box a. The range of values: This technique is used to reduce test case. In this technique, the initial and final values are analyzed. This means that a larger amount than the maximum amount allowed and a little less than the smallest allowable value is selected. b. division: This technique is a way to limit the Test Case. The data is divided into two licit and illicit and both are used in the testing process. c. guess error: The previous experience and weak human use [9]. V.II-Testing White Box This is done by looking closely at the software has created a test based on the condition and inner rings are software codes. Which is sometimes also called structural testing, a test in which the internal mechanism of the system 1444 International Journal of Mathematics and Computer Sciences (IJMCS) ISSN: 2305-7661 Volume.43 2015 www.scholarism.net is also tested. Figure 2 shows the scheme of White Box Testing. int callinfunction() input output {long int test1: Int test2; Figure 2: Scheme Testing White Box [9] This method can cover all software codes. Naming the colors is due to testing methods, the transparency test to be determined. In testing Black Box testing software program does not have access to the source code. The application can be considered as a black box inside the box is not visible. Tester knows only one data series should be inserted into software and to exchange data software will generate a series of output. The White Box Testing focused on the internal structure of the code is [12]. White Box Tester knows the code and data structure designed to test the specific method to be performed with certain parameters. Therefore, unlike testing Black Box, White Box Testing requires knowledge of programming. V-III-testing Gray Box The way to test software with little knowledge of the internal workings of the program. This test is a combination of black box testing. Gray-box testing the internal structure and structure documentation program knows all the data has access. This enables access to good algorithms used and combine them to better Test Case design. Compare the three methods of software testing As you know, in black box testing the internal structure of the program do not know but the white-box testing are fully aware of the internal structure. But in the gray box testing is aware to some extent of the internal structure of the program, which includes access to internal data structures and algorithms for Test Case is designed. 1445 International Journal of Mathematics and Computer Sciences (IJMCS) ISSN: 2305-7661 Volume.43 2015 www.scholarism.net Disadvantages Advantages Software testing methods 1. Lack of knowledge of software 1. find out the problems in the application algorithms 2. Cheap, wasting less time to do the test 2. Lack of expertise testers 3.
Load more

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]
  • 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]
  • 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]
  • 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.
    [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]
  • Software Testing – Levels, Methods and Types
    International Journal of Electrical, Electronics and Computer Systems (IJEECS) ________________________________________________________________________________________________ Software Testing – Levels, Methods and Types Priyadarshini. A. Dass Telecommunication Engineering, Dr Ambedkar Institute of Technology, Bangalore, India 3. System Testing Abstract-- An evaluation process to determine the presence of errors in computer Software is the Software testing. The 4. Acceptance Testing Software testing cannot completely test software because exhaustive testing is rarely possible due to time and resource constraints. Testing is fundamentally a comparison activity in which the results are monitored for specific inputs. The software is subjected to different probing inputs and its behavior is evaluated against expected outcomes. Testing is the dynamic analysis of the product meaning that the testing activity probes software for faults and failures while it is actually executed. Thus, the selection of right strategy at the right time will make the software testing efficient and effective. In this paper I have described software testing techniques which are Figure 1: Levels of Testing classified by purpose. 2.1 Unit Testing Keywords-- ISTQB, unit testing, integration, system, Unit Testing is a level of the software testing process acceptance, black-box, white-box, regression, load, stress, where individual units/components of a software/system endurance testing. are tested. The purpose is to validate that each unit of I. INTRODUCTION the software performs as designed. A unit is the smallest testable part of software. It usually has one or a few Software testing is a set of activities conducted with the inputs and usually a single output. Unit Testing is the intent of finding errors in software.
    [Show full text]
  • International Journal of Computer Engineering and Applications, Volume XII, Special Issue, April- ICITDA 18, ISSN 2321-3469
    International Journal of Computer Engineering and Applications, Volume XII, Special Issue, April- ICITDA 18, www.ijcea.com ISSN 2321-3469 SOFTWARE TESTING Rajat Galav1, Shivank Lavania2, JayShankar Sharma3 1, 2, 3 Department of Information Technology ABSTRACT Testing plays an important role to assure the quality of software. Testing is a process of detecting errors that can be highly effective if performed rigorously. The use of formal specifications provides significant opportunity to develop effective testing techniques. There are three different methods that can be used for software testing. First one is Black- Box Technique, in this technique tester test without having any knowledge of the interior workings of the application. Second is White-Box technique, in this technique the tester needs to have a look inside the source code and find out which unit/chunk of the code is behaving inappropriately. And third is Grey-Box technique, in this technique tester test the application with having a limited knowledge of the internal workings of an application. Our motive to write this research paper first is to research on software testing techniques and their different types which are already developed and can be developed in future. Keywords— Black box, formal technique, Grey box, Motive, Software testing, White box [1] INTRODUCTION Software testing is important activity in Software Development Life Cycle. Software testing is the process of checking the product correctness and finding errors to confirm correct execution. The testing of software is an important means of assessing the software to determine its quality. Since testing typically consumes 30 to 40%of development efforts, and consumes more effort for systems that require higher levels of reliability, it is a significant part of the software engineering.
    [Show full text]