IndexAbstractIntroductionObjectives of Software TestingTerms Associated with TestingBlack Box Testing - StepsAdvantages of Black Box TestingSummaryConclusionReferences:AbstractSoftware testing is the main source of testing that makes our software efficient in functioning. It is even impossible sometimes to declare whether the testing phase has been completed or not. Black Box Testing is an external test. Black Box Testing selects test cases based on an analysis of the specifications of a component or system without reference to its internal structure. It's like a software program, in the eyes of the tester it's like a black box; inside which you cannot see. Say no to plagiarism. Get a tailor-made essay on "Why Violent Video Games Shouldn't Be Banned"? Get an Original Essay Introduction Software testing helps stakeholders judge the quality of their product. Software testing allows the user to generate an independent view on the quality of the product. Testing techniques are a process or application used with the intent of finding bugs in the software or application. It is also used to validate and verify a software program/application or product. Software testing can be implemented at any point in the development process. Most of the testing effort occurs after the requirements have been defined and coding has been completed. The testing methodology is governed by the software development methodology adopted. Objectives of Software Testing Basically software testing is the way to detect errors from the software part of the program where conditions are tested to make the product more efficient and convenient. The main purpose of software testing is quality assurance, reliability, validation and verification. To maintain originality and make software functions work properly, testing is necessary. It is considered a successful test if it uncovers discovered errors. The better the software works, the more efficient it can be used. It includes the correctness and completeness of the software. It ensures the quality of the software element by testing the software element under certain conditions. Terms associated with testing Quality assurance: all those planned or systematic actions necessary to provide certainty that a product or service is of the type and quality needed and expected by the customer. Reliability - This is another term for consistency. If a person takes the same personality test several times and always gets the same result, this is called a reliable state. Verification: is the process of evaluating a system to determine whether a particular product meets the conditions imposed at the beginning of that phase. Validation: is the process of evaluating a system during or at the end of the development process to determine whether it meets the conditions.Black Box Testing. This type of testing includes only the internal workings of the software. In this, the tester does not access the source code. The tester will interact with the system's user interface by providing inputs and examining outputs without knowing how and where the inputs are processed. The representation of Black Box testing is given in Figure 2 below: Test Technique Test Methods Classification of Test Technique (Black Box) Boundary Value Analysis - Errors tend to occur at the boundaries of equivalence classes rather than the "center" ". Requires the program to distinguish between numeric and non-numeric values. Equivalence partitioning: Divides test cases into "equivalence classes". Each equivalence contains a set of "equivalent" test cases. Two test cases are considered equivalent. If you expect the program to process two test cases in the same way, test only one of them, reducingthus the number of test cases to run. Orthogonal/array testing: is a systematic and statistical way of testing used when the number of inputs to the system is small, but too large, to allow exhaustive testing of every possible input to the systemsystems. Fuzz Testing - Fuzz Testing is a testing technique that can however reveal important bugs in your programs. It can identify real-world failure modes and flag potential attack avenues that should be plugged in before software ships. Graph Base Test: Graphs are generated and cyclometric complexity is considered when using test cases in the Graph Base Test. All Pairs Test: Allows you to create a series of tests, using pairwise combination methods, reducing different combinations of variables into a smaller set that covers most situations. State Transition Test: State transition test is used in “finite state machine”. The system can be in a (finite) number of different states, and the transitions from one state to another are determined by the rules of the “machine”. This is the model on which the system and tests are based.Black Box Testing - StepsI. Initially the system requirements and specifications are examined.II. The tester chooses valid inputs (positive test scenario) to check whether the SUT processes them correctly. Some invalid inputs (negative test scenario) are also chosen to verify that the SUT can detect them.III. The tester determines the expected outputs for all these inputs.IV. The software tester builds test cases with the selected inputs.V. The test cases are executed.VI. The software tester compares actual outputs to expected outputs.VII. Any defects are corrected and retested. Comparison between Black Box and White Box Testing Black Box Testing White Box Testing Black Box Testing is a software testing method in which the internal structure of the tested item is not known to the tester It is a higher level of testing Independent software testers are responsible of Black Box TestingKnowledge of programming is not required for Black Box TestingKnowledge of implementation is not required for Black Box TestingBlack Box Testing is a software testing method in which the internal structure of the element to be tested is known to the tester .It is a lower level of testing Software developers are responsible for white box testing. Programming language is required for white box testing. Knowledge of implementation is required for white box testing. Advantages of Black Box Testing Ease of Use: Black box testing does not involve the internal functionality of the application so it is easy to use Tests can be performed easily by technical users. Faster test case development: Testing is about the graphical user interface. In this case the identification of internal routes is not necessary. The tester will cover the GUI paths involved in the specific process. Simplicity: Using Black Box Testing you can test even complex applications by focusing on valid and invalid inputs and ensuring that the correct q24out puts are received. A Better Look at the Black Box TestBlack-box Tests seem to stand out because they focus on the end user; that undertaking black-box testing is the best way to ensure that those parts of the applications that will be exposed to the user function correctly. Combined with ease of use, faster test case development, and simplicity, black-box testing represents a lower initial cost than white-box testing and provides ROI in a shorter period of time. Recognizing that this is the case, faced with budget and time constraints, black box testing must be