Conflict testing in Software testing

Transferred from: http://www.51testing.com/html/54/n-247254.html

absrtact: This paper introduces a testing method in our company--the meaning of conflict test, and makes a brief introduction about conflict test in our scope of use and the design method of conflict test case .

　　Keywords: conflict testing

　　1 , what is a conflict test

Conflict testing is a term within our company that may be different from one company to another. Our company's so-called conflict testing refers to the testing of interference by third-party functions or software when running a function of a program . The test method simulates a test based on a software state scenario. From the running state of the software, we think that the state of the software is generally only start, hang, end, these three kinds of States. The conflict test is the test that simulates the interfering software running the start, suspend, and end states.

　　2 , application scope of conflict testing, and some application scenarios

The test method of conflict testing is common in the fields of mobile phone Software testing , mobile communication embedded software testing and so on. But in some desktop software or web system testing field can also be applied, but the application of the scene is not as wide as mobile communication software.

Here's a brief introduction to the typical scenarios in its different software types:

Mobile software:

For example, when receiving text messages, the scene of a telephone call;

During video playback, USB is plugged in;

During the call, I received a text message and so on.

Mobile Communication class Embedded software:

Mobile communication embedded software, mostly based on 3G network application software. For example, some in-vehicle software, such as the terminal installed in the car, you can achieve similar based on mobile phone functions, and integrate the functions of Internet Entertainment software. Typical software types, such as Toyota's "G-book", BYD's "I" System and so on.

The test scenario is as follows:

In the process of downloading the navigation, an instant message was sent;

In the process of playing music, a call came in;

During the Bluetooth connection, a new Bluetooth connection request was received and so on.

Desktop software or web system:

Desktop software or web system conflict testing, common in multi-threaded programs, with multi-system cooperation programs, multi-rights management program.

Multi-Threaded Threads:

For example, a query function, because of a lot of data, after the query has a waiting to load the completion of the state thread. At this point we can close the waiting state thread by closing the label or page;

There is a function to export data, in the export data waiting process, close the label or page, the end of the waiting state thread.

........................

　　3 , the position of the conflict test should be in the whole test

　　The position of the conflict test in the entire test should be the same as in the boundary value Test . This type of test should also be considered when designing test cases. Based on the experience of testing this test method in the past, this kind of testing often leads to some more serious problems. For example, the above prompt to "in the video process, inserted USB", caused by the phone software black screen, and can not restore the P1 level problem; "In the process of downloading navigation, an instant message", causing the car navigation function in the interface to die, only restart to restore the software operation problem; "Query function, Because of the large amount of data, there is a status thread waiting for the load to complete after the query. At this point we end the waiting state thread by closing the tab ", causing the desktop software to crash completely, only through the process to the end of the problem can be restored, the multi-system cooperation program that example, in the forum system we have done, has caused the issue of the passage of the article was published.

Why does the conflict test have the same status as the boundary value test method?

Because frankly speaking, conflict testing is a concrete embodiment of boundary value method test method. There is a small misunderstanding of the boundary value method, whether it is in the book or on the network usually speaking of the boundary value method, the example is often the number of boundaries, that an input box can only be 20 characters when we test its 21-bit characters, it is certainly not wrong, but often this past, Many testers consider the boundary value method to be the data boundary. In fact, I think the boundary value method includes three kinds: the boundary of the input action, the boundary of the number, and the boundary of the state. The boundary of the so-called input action, such as the query has three input boxes, a box is not input to query, this is the boundary of an input action. The quantity boundary, which is the minimum and maximum number of a value. State boundaries, which are the three states of start, suspend, end. Since the focus of this article is on the method of conflict testing, there is no further meditation on the boundary value.

4. Design method and execution strategy of conflict test cases

This kind of test case design method is basically the same as other types of use case design methods. However, different software types have a slightly different focus on their use-case design approach. Let's take a look at the general method and execution strategy of the use case design for mobile and mobile-type embedded systems:

A) identify functions that can interrupt other functional states.

such as mobile phone functions: General calls, Bluetooth, SMS, MMS, Alarm clock, USB, charging and other functions, will pop up a hint information layer. Therefore, the conflict test cases must consider whether this function can cause some exceptions when interrupting other programs.

B) traverse all function modules

Analyze the usage frequency of the function module, divide the different frequency module according to the different level, in order to be advantageous to the test strategy arrangement.

C) Execution Strategy

One of the difficulties of such testing in mobile communication software such as mobile phones is to find out the test time points. Because it happens very quickly when you perform a function, it's time to break that state. This, I would like to do the mobile phone software testing comrade is very clear. The method I used is generally performed by using the phone stopwatch function to calculate and time out the average time after the function has been calculated and counted. In addition, this type of use case should perform the highest-level use case at the previous stage, and the combined policy is sorted by the principle of traversing all levels in multiple versions at the middle and later stages.

5. Examples of conflict test cases

Some use cases for mobile phone software, such as SMS modules:

Module	Use case overview	Test steps	Expected results
SMS Module	To call	1. From the main menu interface into the SMS interface process, there is a phone call in	1. Phone calls normally, still in the main menu interface
SMS Module	To call	1. In the process of entering the text message interface, there is a telephone call in	1. Phone calls normally, still highlighted in the text message menu
SMS Module	To call	1. In the process of sending a message, there is a phone call in	1. Incoming phone calls normally, this message fails to send, keep in inbox
SMS Module	To the alarm clock	1. From the main menu interface into the SMS interface process, the alarm time to	1. Normal pop-up alarm, after turning off the alarm, still in the main menu interface
SMS Module	To the alarm clock	1. In the process of entering the text message interface, the alarm time	1. Normal pop-up alarm, after turning off the alarm, still highlight in the text message menu
SMS Module	To the alarm clock	1. In the course of sending SMS, the alarm clock time	1. Normal pop-up alarm, after turning off the alarm, the text message fails to be sent, keep in inbox

....

Conflict testing in Software testing