Shulou(Shulou.com)06/03 Report--

A new category will be added to the business line, which is not much different from the original classification, but due to major changes in vendors, server architecture, interfaces, etc., it is still necessary to fully test the newly added category.

At the same time, because the overall process and functions are roughly the same as the original classification, after comprehensive consideration, it is decided to use the previously classified test cases, so it is necessary to add, delete and modify the previous use cases and update the previous use cases immediately according to the new requirements and new version.

After taking a closer look at the previous use cases, it is found that the use cases are written from a page to a function, and then run a dozen business processes.

For this kind of design idea, there are the following thoughts:

(1) on the whole, this design idea is first function, then process, followed by function, followed by process, and there is a distinction between function and business process use case. in execution, testers can focus on a certain page or a certain function for testing. it is not distracted by frequently paying attention to the switching between functions and processes in the testing process.

(2) individual functions and pages are fully tested. There are test cases for every page and every function, and there are enough tests for functions and pages, and there are few omissions in this aspect, which fully ensures the comprehensiveness of functional testing.

(3) it is helpful for writers and newcomers to have an in-depth understanding of all pages and functions. Use cases are written according to each function of each page, so there are more reliable and complete tests for all possible pages and functions, whether for old employees or newcomers who write use cases, in terms of promoting an in-depth understanding of the features. are of great help.

(4), the requirement for the writer to understand the business process is very high, and the learning cost is relatively high, but for the whole process of writing, it is relatively simple and smooth. When writing a use case, the person who needs to write the use case should have a very in-depth understanding of the overall business process and each possible page, which generally takes a relatively long time, and the learning cost is relatively high. there is great resistance for newcomers to quickly understand the overall business process and use case design ideas. However, as long as you have a good understanding of the page and functionality, it is relatively simple and smooth to write use cases.

(5) frequently switch the test entry, increase the execution cost and steps, so that the execution time can not be evaluated accurately and effectively. Each use case related to each page or function is interrelated, while the use case between the other processes is relatively independent, so it often occurs that the previous use case is only one step away from submitting the order, and by the next use case, it inexplicably jumps to another classified order submission page, and the steps are pitifully few. Only the preset condition says that it is on the filling order page of a certain category, and the use cases are interrelated or even dependent on each other. Switching entrances so frequently increases the difficulty and steps of test case execution, which is disadvantageous to evaluate the execution time and the overall test time according to the number of use cases.

(6) the process testing is relatively insufficient. Taking into account the business processes that have been executed at the same time for functional testing, coupled with the specially executed business process use cases, a total of more than 20 business process use cases have been executed, and after combining according to the various conditions of the overall business process, it is found that if all conditions are taken into account, there are thousands of business process combinations, cross-combining in the case of compressed conditions as much as possible, and there are more than 100 business processes. Even if repetitive or non-existent processes are removed, there are at least dozens or even hundreds of possible combinations. Obviously, the previous use cases did not fully consider the composition of the business process, and there were omissions in the business process.

(7) when performing the process test, it is inevitable that there will be repeated execution of the functional test.

In order to avoid process omissions and the execution time is controllable, it is decided to take the time to transform the use case as a whole.

The initial idea is relatively simple, since the previous use cases are function-based, followed by the process, then take it for granted that the change to process-based, followed by function. However, there are the following problems:

(1), the business process will be more fully tested, but for pages and functions, there will inevitably be omissions, especially some exception pages and functions with few opportunities. Moreover, the testing of pages and features will inevitably be inadequate. How to determine the relationship between the two?

(2) are the tests for pages and functions screwed out separately or interspersed with tests? If you screw it out separately, will there be repeated execution, or will it be omitted?

(3) how to screen the process to ensure that the process testing is as adequate as possible? How to make sure that the process is fully tested?

(4) how to balance the number of use cases and the adequacy of tests? If you want to fully and fully test, there are thousands of optical processes, and the quantity is too large, so you have to doubt your life even more. How to determine the balance between quantity and adequacy?

All right, after you have finished reading the article, I will share some information with you.

Information related to interface testing

Link: https://pan.baidu.com/s/1ojpoWnpxxReR1sO2Gxy_YQ password: dgfa

Data related to performance testing

Link: https://pan.baidu.com/s/1_oZhvOIRvcz0JGcCWUGT-g password: d82b

Introduction to software testing to improve e-books

Link: https://pan.baidu.com/s/1Fp8CFE0D2p0uAZk6xcexhQ password: exna

Data related to automated testing

Link: https://pan.baidu.com/s/1yeD1EMg-HalNuRBDODGx7g password: ofdg

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.