As a test team, the basic duties are: test product, find defects, reporting results , so that each version of the test level steadily. These values are used as a test must have played these values can make the test to get the basic trust R & D team.
Such value is divided into three parts:
1) intercept defects , namely to test the product, as far as possible interception of defective products in the development stage.
2) providing data , i.e., to provide quality products conclusion, these results support and gives data.
3) testing process controllability , enhance the ability of the test team and test engineers, so that the efficiency of product testing, quality and costs are under control.
"Minding" describes these values are basically testing their own work , play value is to rely on self-test or to test based capacity building. Of course, this does not mean that they must be tested to the limit value, test engineers also need to weigh the costs and benefits to find the right "degree."
Intercept test defect is the most basic value, as much as possible to find defects, as far as possible to find and solve affect users of the defect before the release , which is the basis for the existence of this career test.
A test team or test engineer, if basic dysfunction will often leak out, it is in any case can not be trusted. This is not to say that as long as there is a legacy product to the customer defects, test activities will certainly have a problem, the ability to intercept defects will certainly need to improve. Usually still depends on the degree of influence of defects may be.
In order to facilitate solutions to illustrate the problem, here in accordance with the activation condition defects (wrong product is activated under certain conditions, cause the product to malfunction, the "specific conditions" is activated condition), the defects are divided into four categories:
A basic functional defects
When the basic operation of the user's normal course of business, due to defects lead to business operations can not be completed. The maximum impact of these defects on the user's problem is the development of the highest priorities.
B defects conventionally used
When in most cases the user can complete the normal business operations, but business operations under certain conditions, lead to defective activation can not be completed, the vast majority of product defects fall into this category. Want to reduce such defects, according to the need for further scope and severity of the failure to find high priority to solve.
C attack exposed flaws
Product failure is not due to the user's business operations, but due to abnormal hardware or network environment, service request volume overload caused by more than expected, subject to hacker attacks. Such defects great impact on the user, but the user will be considered based on the cost of the settlement, not necessarily all be solved through enhanced software capabilities.
D random defects occur
Conditions product failure is not clear if the scope of the failure of large, high-severity, high frequency of appearance, will conduct a special analysis of the defect.
3.1 users can not use normal
Typical of such defects are: An error occurred during the installation or upgrade, the basic functions of newly developed properties are wrong, the original function properly after the upgrade using the wrong products several times a collapse in normal use, normal use has led to direct economic losses of users or information leaked error.
3.1.2 idea to solve the problem
[General principles]
after the product is installed or upgraded, the basic functions of error or totally unusable, which is a great harm to the credibility of the tests, if these errors occur often repeated, the test need to intercept the defect as a top priority.
[Solution]
found conditions such defects are: coverage to the test as long as this feature or characteristic, it is possible to find defects. Therefore, in the face of such problems, the recommended solution ideas are:
1) to establish basic test baseline (baseline test is similar to the code base, is off to a version of the product, the product of all the test cases and test results collection, which is the basis for the next test version of a product, so called baseline. the basic test is a subset of the baseline test baseline), a basic test suite that contains the product of the most common business scenarios, covering most of the features.
2) as close as possible to 100% test automation, test before each start, product launches will test basic test all over again.
3) Sometimes the problem is also related to customer data, the environment, the use of the method, the basic test cases with a baseline of information on the need to include customer data, environment, scenarios, etc., press release, customer management.
3.1.3 establish a baseline test case
Our main products are required to establish a baseline test, baseline use case contains the basic use cases, routine use cases, uncommon use cases. The basic use case is a set of basic use cases mentioned sections. General use cases include the vast majority of normal and abnormal case, the general characteristics or modify the old new feature has great influence on the characteristics of the old, conventional use case will test the old characteristics. Some uncommon use case is to use unconventional means to test the implementation of such violent attacks, power outages, code injection, etc. These use cases are rarely repeated testing, re-testing will consider only the reliability, security architecture to do the upgrade.
Construction standards baseline test case contains the basic requirements and additional requirements of section 2, the basic requirements of the integrity of the test focuses on the baseline; additional requirements baseline test case focuses on whether easy to use.
[Basic requirements]
1) product-level test cases to establish a baseline, baseline characteristics of the products covered all functions and all quality attributes (features, performance, reliability, security, serviceability, data). Product-level meaning that a product with a baseline set of cases, rather than a version with a baseline cases, which is at all times in order to get an overall view of the quality of products based on the test results of the use case.
2) a set of test cases in the baseline or use case, comprising, a correspondence relationship with the demand of product characteristics. This is in order at the end of the test, according to the characteristics or needs analysis of test results.
3) a baseline test set comprising the basic use cases, product characteristics method covers substantially 100%. This requires that each product have at least one characteristic use embodiment are substantially in focus with the embodiment.
4) use the baseline test cases with empty cases, a copy cases, automated script text, and the absence of other inconsistencies. This embodiment is the most basic quality requirements.
[Additional requirements]
1) a baseline test cases cover all the needs of the product.
2) an update for test baseline audit. To do a baseline test and product updates synchronization, each version refresh baseline characteristics change according to circumstances, to ensure that the baseline is not corrupt.
3) There are cases of baseline management tools, tools for managing all of the information on the use case and its implementation process and results, and can easily query depending on the version, customers, business conditions, and the evolution of the test results analysis.
3.1.4 To synchronize the baseline test case management and quality optimization
In common, proven software, there are some examples of "user can not use normal".
Want to find the flaw in the test, necessarily need to have a business with a baseline scenario cases, this new version validation, to be able to find that there has been loss of properties, business scene has some defects can not be achieved. Test to establish the baseline not simply use the existing embodiment to manage and automate, it may be necessary to improve the quality of use of the embodiment, on the one hand needs to be designed in accordance with embodiments of business scenario, on the other hand in the preset condition, the steps, intermediate and final check the terms of the results need to be more rigorous.
In the course of each product in this capacity-building, some products directly to the basic function of the characteristics of the test cases used to construct basic verification test at baseline, after using the findings do not block "the user can not use the normal" defects, so that the basic baseline test case "useless." But in fact this is not the basic baseline test method is not used, but the baseline does not cover cases using the user's normal usage scenarios, or scenario covers the inspection result of the content, but incomplete.
3.1.5 find a test case to establish a baseline for the crux
In the pre-established baseline test work, I suggest and service representatives, representatives of the market, R & D managers do full communication. The best performed shift in thinking: the perspective of the design verification test into a demand for verification, validation scenarios; first consideration is to solve business problems rather than automated methods.