Table of ContentsSummaryIntroductionObjectives of Software TestingTerms Associated with TestingBlack Box Testing - StepsBenefits of Black Box TestingSummaryConclusionReferences:SummarySoftware testing is a major source of testing that makes our software effective in its operation. Sometimes it is even impossible to declare whether the testing phase is completed or not. Black Box tests are external tests. Black Box Testing selects test cases based on an analysis of the specification of a component or system without reference to its internal structure. It's like software, in the eyes of the tester, it's like a black box; inside which we cannot see. Say no to plagiarism. Get a tailor-made essay on “Why violent video games should not be banned”?Get the original essayIntroductionSoftware testing helps stakeholders judge the quality of their product. Software testing allows the user to generate an independent view of product quality. Testing techniques are a process or application used for the purpose of detecting bugs in a software or application. They are 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 testing efforts take place after requirements have been defined and coding is complete. The testing methodology is governed by the adopted software development methodology. Objectives of Software Testing Basically, software testing is the way of detecting errors in a software element of the program where conditions are tested to make the product more efficient and profitable. The main objective of software testing is quality assurance, reliability, validation and verification. To maintain originality and make software functions work correctly, testing is necessary. A test is considered successful if it reveals discovered errors. The better the software works, the more efficiently it can be used. It includes the correctness and completeness of the software. It guarantees the quality of a software element by testing a software element under certain conditions. Conditions associated with TestingQuality Assurance - All planned or systematic actions necessary to ensure that a product or service is of the type and quality required and expected by the customer. Reliability – This is another term for consistency. If a person takes the same personality test several times and always obtains the same result, it is called a reliable state. Verification - It is the process of evaluating a system to determine whether the given product meets the conditions imposed at the beginning of this phase. Validation - It is the process of evaluating a system during or at the end of the development process to determine whether it meets the requirements. Black Box Testing. This type of testing only includes 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 used. 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 classes d equivalence rather than at the “center”. It requires the program to distinguish between numeric and non-numeric values. Equivalence partitioning – It divides test cases into “equivalence classes”. Each equivalence contains a set of “equivalent” test cases. Two test cases areconsidered equivalent. If you expect the program to treat two test cases the same, test only one, thereby reducing the number of test cases you need to run. Orthogonal/Table Testing – This is a systematic and statistical testing method that is used. when the number of inputs in the system is small, but too large, it is possible to exhaustively test every possible input in the system.systems. Fuzz Testing - Fuzz Testing is a testing technique that can nevertheless reveal significant bugs in your programs. It can identify real-world failure modes and flag potential attack avenues that need to be closed before your software is delivered. Graph Base Testing - Graphs are generated and cyclometric complexity is taken into account when using the test cases in graph base testing. All-Pairs Test - It allows you to create a set of tests, using pairwise combination methods, reducing multiple combinations of variables into a smaller set that covers most situations. State Transition Testing – State transition testing is used in the “finite state machine”. The system can be in a (finite) number of different states, and transitions from one state to another are determined by the rules of the "machine". This is the model on which the system and the tests are based. Black Box Testing - StepsI. First, the system requirements and specifications are examined.II. The tester chooses valid inputs (positive test scenario) to check if SUT processes them correctly. Some invalid inputs (negative test scenario) are also chosen to verify that the SUT is able to detect them.III. The tester determines the expected outputs for all these inputs.IV. The software tester constructs test cases with the selected inputs.V. The test cases are executed.VI. The software tester compares the actual outputs with the expected outputs.VII. Defects, if any, are corrected and retested. Comparison of 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 item under test is not known to the tester. higher level of testingIndependent software testers are responsible for Black Box testing.Programming knowledge is not required for Black Box testing.Implementation knowledge is not required for Black Box testing.Black testing Box is a software testing method in which the internal structure of the item under test is known to the tester. .This is a lower level of testing. Software developers are responsible for white box testing. A programming language is required for white box testing. Implementation knowledge 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 hence easy to use. Testing can be easily performed by technical users. Faster test case development – ​​Testing issues with GUI. Identifying internal paths is not necessary in this case. The tester will cover the GUI paths involved in a specific process. Simplicity - With black box testing, even complex applications can be tested by focusing on valid and invalid inputs and ensuring that the correct q24out inputs are received. Testing seems to stand out because it focuses on the end user; that undertaking black box testing is the