Calculator Software Testing

Calculator Software Testing
Calculator Program Testing
Name of Student
Course Name
Professor’s Name
University Name
Date

Calculator Software Testing
Executive summary
Subsequent to leading a serious research, I thought of this report relating all the data
concerning program testing. This report gives a more comprehension of various software
testing methods and program testing tools. Additionally, works from various Authors
concerning the same have been given a genuine study and an audit is given on the same.
The program under appraisal in this venture is the Calculation Program code. Distinctive tests
were performed on it checking its validity and vulnerability in its use. These tests
incorporated its ease of use, similarity, execution and security. It was uncovered that without
these tests, the program would have acquired poor outcomes to its delivery process.
The discoveries found in the research are that in the bug fix, designers experience a few
issues. Above all else, in the correcting the bug, they may present other unintended bugs. It's
a great risk they take however it must be embraced. Additionally, white box scanners explore
shortcomings in security for all applications.
The exploration reveals the way that logical virtual softwares are inclined to bugs and
henceforth testing can never be exhausted. Bugs are reliably showing up along these lines a
test was made to decide the strategy of recognizing them, gaining power of them and not
concealing their manifestations. Notwithstanding that, testing devices, for example, Selenium
RC have decreased the exertion in the testing process by opening and shutting databases and
coordinating information being tried with the information put away in databases (Altaf,
2015). Besides, it was understood that through the four measurements of testing, another
measurement should have been incorporated which is a logical analyzer as a feature of the
testing framework (Kelly, 2011). By incorporating the logical analyzer in the framework, the
analyzer will be recognizable furthermore, thorough with the software.
It is suggested that, the issue of oracle ought to be put into consideration when developing
testing systems, the code that is acquainted with fixing a bug ought to be analyzed to avoid
from presenting different bugs, discovery white box testing tools ought to be put in place
when checking the helplessness of a web application's security, system analyzer have to be
incorporated into the testing procedure, Junit test is best trying instrument for checking
applications quality and at long last, testing is unavoidable during the time spent making a
logical application program.

Calculator Software Testing
Table of Contents
Executive summary...............................................................................................................................2
Introduction...........................................................................................................................................4
Literature review...................................................................................................................................5
Testing techniques.................................................................................................................................8
Boundary value testing..................................................................................................................8
Equivalence class testing...............................................................................................................8
Programs and Tools for testing..........................................................................................................8
Test cases..........................................................................................................................................9
Functional test...................................................................................................................................9
Experimental tests...........................................................................................................................10
Figure 1.0.....................................................................................................................................10
Figure 1.1.....................................................................................................................................10
Conclusion...........................................................................................................................................11
References...........................................................................................................................................11

Calculator Software Testing
Introduction
The aim of this report is to bring into being the different methods for testing a software and
fixing its bugs. Also to understand different techniques used in testing and testing tools in real
life when testing a picked program in its study.
Several requirements are needed to test a software or fix its bugs. These are the testing
methods and the testing tools. In the testing methods, there are a few techniques that are
relevant: the black box, white box and the grey box techniques. However, before we go into
better terms about the testing methods, we should first characterize what a software is testing.
For the most part, it is a test to check the nature of the software and to check the mistakes that
may have emerged in the development of the software. Likewise checking if the software has
met its prerequisite is a testing process.
Diverse methods have distinctive approaches in the checking the vulnerability of a program.
The white box technique, checks if the software has met the prerequisites that were put down.
It determines that the outcome is the normal one by survey the internal functionality of the
program and looking at the outcome. This strategy does is required to examine the internal
working of the program. Its outcome affirms everything ranging from the internal validation
of the program. Aside from white box we have another testing technique, the black box
strategy. Black box technique explores the graphical user interface of the program. This
technique looks at the code and recognizes where the issue is and furthermore checks if the
outcome meets the necessities put down. The grey box method, a "cross breed technique",
joins both the white box what's more, the black box useful attributes. The analyzer has
constrained information of the working of the software. It is therefore compelling contrasted
with black box strategy where the analyzer just looks at the software physical layout.
I used the Calculator program software to be tried with the TestNG, Yasca and Selenium
testing tools. The scrutinized for testing is the grey box technique. These practical
prerequisites are: contributing information easily since the user interface is inviting, the
elements of the applications are effortlessly identifiable (performing correct arithmetic
through its interface buttons), the software can be effectively analyze (show of things to be
calculated) and the undertaking to be executed is done immediately. This application has
made things simple and furthermore transactions are enhanced since it tends to be finished
remotely. Calculator program utilizes for its activity consequently it tends to be access widely