14th Week Summary

Software Testing Methods

White box test

The white box test is to think of the test object as an open box.      When using the White-box test method for dynamic testing, it is necessary to test the internal structure and processing process of software products without testing the function of software products. The coverage standard of the White box test method is logic overlay, loop overlay and basic path test.      The logic overrides include statement overlay, decision overlay, conditional override, decision/condition overlay, conditional combination override, and path overlay. White box testing is to know the internal work process, can be tested to detect whether the internal action of the product according to the specifications of the normal, according to the procedures within the structure of the test procedures, the test procedures in each path is able to work according to predetermined requirements, regardless of its function, the main method of white box testing has a logical drive,      Base-Path testing, etc., primarily for software validation. White box test common tools are: Jtest, Vcsmith, jcontract, C + + test, Codewizard, Logiscope.black box TestBlack-Box testing is a software test based on the specifications of the software, which does not take into account the workings of the software, so the software is like a black box for the user. Software testers to the user's point of view, through a variety of input and observation software of various output results to discover the shortcomings of the software, and do not care about how the program implementation of a software testing method. Black box test common tools are: Autorunner, WinRunnerAutomation

Using automated test tools to test, such tests generally do not require human intervention, usually in the GUI, performance and other testing and functional testing more. Automate the test process by recording a test script and then executing the test script. The domestic leading automation testing service provider is Ze Zhong software. Automated testing tools include QTP, Testcomplete, Autorunner, and tar.regression testRegression testing is the re-testing of previous tests after a change has occurred to ensure the correctness of the modifications. In theory, a new version of the software will require regression testing to verify that the errors previously discovered and repaired are re-emerging on the new software version. Re-test according to the repaired defect. The goal of regression testing is to verify that defects that have been previously seen but have been repaired are no longer re-emerging. Generally, the defect of a known fix is re-tested again around the step in which it originally appeared. It is often difficult to determine the extent of the required re-testing, especially when near the product release date. Because it is necessary to change the source code in order to fix a flaw, it is possible to affect the functionality that this part of the source code controls. Therefore, when verifying the repaired defect, not only will it be subject to the steps of the defect to be re-tested, but also all the functions that may be affected will be tested. Automated testing of all regression test cases should therefore be encouraged.Acceptance TestingAcceptance testing refers to a phase of the system development life cycle methodology, when the relevant user or independent tester tests and receives the system based on the test plan and results. It lets the system user decide whether to receive the system. It is a test that determines whether a product can meet the requirements of a contract or user. Acceptance testing generally has three strategies: formal acceptance, informal acceptance or alpha testing, and beta testing.Static TestingA static test is a part of a test that does not run, such as a test product specification, which is checked and reviewed. Static method is to not run the program itself, only by analyzing or checking the source program grammar, structure, process, interface, etc. to check the correctness of the program. Static methods through the analysis of the static characteristics of the program to find out what is missing and suspicious, such as mismatched parameters, inappropriate loop nesting and branch nesting, disallowed recursion, unused variables, null pointer references and suspicious calculations. Static test results can be used for further error checking and provide guidance for test case selection. Static test commonly used tools are: Logiscope, Prqa;Dynamic TestingDynamic testing refers to the correctness of the software's dynamic behavior and running results by running the software. According to the stage and function of dynamic testing in the process of software development, dynamic testing can be divided into the following steps: 1, Unit Test 2, Integration Test 3, System test 4, acceptance Test 5, regression testUnit TestUnit tests are the smallest scale of tests, to test a feature or block of code. It is typically done by programmers rather than testers, because it requires knowledge of the details of internal programming and coding. This work is not easy to do, unless the application system has a well-designed architecture; You may also need to develop test drive modules or test kits.Integration TestingIntegration testing refers to the joint testing of individual components of an application system to determine whether they can work together without conflict. A part can be a block of code, a standalone application, a client on a network, or a server-side program. This type of testing is especially relevant to client servers and distributed systems. Before the general integration test, the unit test needs to be completed. Integration testing is a logical extension of unit testing. Its simplest form is: Two tested units are assembled into one component, and the interfaces between them are tested. In this sense, a component refers to an integrated aggregation of multiple cells. In a real-world scenario, many units are assembled into components that are then assembled into a larger part of the program. The method is to test the combination of fragments and eventually extend the process to test your module with the other group's modules. Finally, all modules that make up the process are tested together. In addition, if a program consists of multiple processes, you should test them in pairs instead of testing all the processes at the same time. Integration testing identifies problems when combining units. By using a test plan that requires testing each cell before the composition unit and ensuring the viability of each unit, it is possible to know that any errors found in the composition of the unit are likely to be related to the interface between the cells. This approach reduces the number of possible cases to a simpler level of analysisSystem TestingSystem testing is a black box test based on the overall requirements specification of the system, which should cover all the joint components of the system.      System testing is a test of the entire product system to verify that the system satisfies the definition of the requirements specification and to identify areas that do not conform to or contradict the requirements specification. The object of system testing is not only the software of the product system that needs to be tested, but also the hardware that the software depends on, the peripherals even include some data, some supporting software and its interface. Therefore, the software in the system must be combined with various dependent resources, and tested in the actual operating environment of the system.

14th Week Summary