Test case granularity specification

Test case granularity specification Three? Five? 10 for fine? The above is fine? To test design ideas? Is it just the forward? Is only positive/negative to be bold? Consider the application scenario as fine? Consider the business logic as fine? By orders of magnitude? Article one hundred? Article one thousand? Article ten thousand? Data coverage? The equivalence class is thick, right? Exhaustion is fine? Everyone, every organization determines that the standards for testing use cases are different and there is no standard answer. So the thickness of the test case granularity is itself a relative standard. Try to illustrate the general concept of granularity by graphing it: What is the characteristic of the test case particle size and detail? Use-case design analysis: The design of the test case is embodied in the macroscopic, the function point of the positive, the large functional module and the whole. The fine particle is microscope.facing the specific function points of the positive/negative logic, the details and completeness of the test case are embodied. Facing the tester: Coarse-grained use cases are not easy to test for novice execution because many conventions, phenomena, and even industry terminology are not clear. Fine-grained use cases are relatively easy to test for novice execution. Coverage: Coarse granularity coverage may less than fine granularity cases (coarse granularity only cover all positive and negative, fine granularity, cover all positive, negative, other, etc.); But there is another possibility, which is that the use cases are all covered, but the depth is different. Unlike rainfall, which varies from rain to rain, the meaning of the crop is different. Maintainability: There is no doubt that the test cases and demand match, the maintenance of the test case itself is the key work difficulty most teams, coarse particle degree is easy to maintain, convenient to maintain highly consistent and requirements; Fine-grained use cases, the thinner the less easy to maintain, the maintenance costs are too large, especially the frequent changes in requirements that cause unmaintainability. Similar concepts, such as automated test links, are similar to the script rewriting that the GUI changes. Time: Coarse-grained architectures and reviews are shorter, suitable for shorter periods; Fine-grained build and write longer, suitable for cycle easing or more quality. Resources: Coarse-grained use of less resources (human, review, conference room, etc.), suitable for small teams or multiple project models of the same team; Fine particle size occupies more resources, suitable for large team or single project model. Risk: There is no doubt that the risk of a coarse-grained use case is a leak, the risk of a large probability leak, dependent on the individual quality of the tester; Fine granularity also has an omission, but it is more likely that the tester's own assumption skipped the use case. The maximum risk of a fine-grained use case is maintainability, or input-output ratio. Test case granularity for routine application scenario enumeration: The above analysis is a lot of test case particle size thick and fine characteristics, so, in general test, how to position test case granularity the thickness of the particle degree? The following is shown in a single application environment. Again, the same thing: the same organization may have different test purposes, perhaps testing different areas or different levels of the same area. A single condition: 1, time factor: The time is short, the project is tight, and the use case review time is shorter, suitable for the use case of coarse grain. When the project cycle is longer, the use case for fine granularity is suitable. Six months of the project such as planning, the planning phase and design phase one and a half months, the early stage of the test, there is enough time for personnel training, writing test cases, need to fine granularity. If the project is for a month, test preparation time only five working days, you may have to complete the first round on the third day of the test case review, suggestion is given priority to with coarse granularity, covers the function and thinking. Project personnel: Use cases of coarse-grained use cases when the tester is more skilled, the thinking and basic skills are solid, or the tester is responsible. Testers are new to the test and need to be guided for basic test work, or when the responsibility is general, use case of fine granularity. The difference between a tester and a novice is obvious. Here, conscientiousness is used as a test case to write a detailed criterion for the test case. In fact, the test personnel's professional quality, there is a sense of responsibility, the quality requirements vary from person to person - and everyone must sense of responsibility also feel good about themselves. For example, for example, installation testing: How to write it: make sure the setup is successful under Microsoft's various operating systems. The responsible person may go through the spec book, confirm the operating system supported by setup, and then install the test in turn. Conscientious people,It may be taken for granted that the transitional version of visia, which is rarely used by a personal user, is simply skipped over the two systems. So for those responsible, you have to write A small use case: installation test: A, installed in the SP2 environment of Windows XP; B, installed in the SP3 environment of xp; C, installation under win server 2000; ... It is. The quality of the project Project quality requirements, or project transition projects, short life cycle; When a project is a temporary project, use cases for coarse-grained use. The project quality is high, the customer or company is the first, the brand project, the use case of fine grain. Aren't all projects high quality requirements? Of course not. The demand for quality is different in different countries and ethnicities: the United States is good enough, Germany is the best, and China is on the spot. Different position in the industry of the company to the quality requirement is not the same: top companies make perfect products, intermediate companies make cost-effective products, the company make cheap products. Different positioning of the company to the quality requirements are not the same: the restaurant to eat at the gate of the railway station is the traffic, in urban areas in remote parts of the hotel food was repeat business. Different purposes of the list is different to the requirement of quality: do zhang kickbacks of virtual project, no use after the bid, three years after the equipment upgrading, quality, there is no requirement. Focus on projects, quality requirements, etc. So, there must be a different quality of the project. Naturally, there are different test strategies and test purposes, and the sequence exports the test cases for different granularity. Resource allocation: A test case for coarse-grained granularity can be used when the resource configuration is less than the refinement of the test case. The resource allocation is more, which can be used for the intersecting of the use case writing, review, and revision, but the fine granularity is applied. Example: if the tester configuration is less, a total of just three to five individuals, each responsible for a project, don't have time to do the review with each other, even the project exists the phenomenon of temporary increase, is impossible the refinement of test cases, even coarse granularity is difficult to achieve, can only pull out a test outline. Or the test team has more than a dozen people, but the project is flowing water. Demand, development, testing is mass line pattern processing projects, cannot do the whole process of participation in a project, it is hard to test case review and revision that refining. Requirements change: When requirements are changed, the use case for coarse granularity is recommended, which can be more flexible to cover requirements. After a round of review, after the requirements baselined, in the actual rolling test, the use case was progressively refined -- based on the actual situation of the project. The less requirements change, or demand change affected small, is not a system design framework of frequent changes, specific evaluation standards require different industrial products, can be corresponding to the larger change quantity of detailed test cases. For example, the use case of coarse granularity for a requirement is 100, and the use case for fine grain is 10000. This requirement changes, if you want to modify the use case for coarse-grained, only 10 changes are required; To modify the use case of fine granularity, involving detailed cross-logic, you need to review 2,000 use cases and may modify 1200. If the test case modifier is not written by the test case, the modification time may be extended by 1.3 times. Project objects: If the project/product is ultimately faced with a specific person, a professional, a technical person, and a trained operator, the use case for coarse granularity can be used. If the project/product is ultimately faced with a broad adoption community, the people's mass consumer, use cases of fine granularity. Project/product for professionals, tend to be positive testing, some problems or use outside the rules, requirements, can be in training or specification specified in the operating mode, or with the technical personnel skills to avoid problems. Project/product for non-specialists to do training and the operating agreement, the use of all kinds of strange method, operation habit, so more inclined to fine granularity, covers the negative and randomization test cases. Test team quality: The team individual quality is higher, can adapt the style of bold, agile, can use the use case of coarse grain degree. When the team is in the early or early stage of the establishment, the use cases of fine grain degree are applied when the rules agreement is detailed. Company decision input: The company's investment in testing, the requirement of product quality, the control of the rhythm of the industry. This paper discusses the quality properties of the project. The other concept of test cases is a detailed description of the use case. (the old text is posted) There are many kinds of documents,You will encounter similar granularity problems when writing test cases in the back. The first is to write to yourself, and to the level of colleagues who understand the technology. This will only require a rough description of the core key points. The second type is for the technical staff, but there is a certain base of the person who is looking at it, so that the basic concept is not described, and the overall step description is clear. The third kind is to don't understand technology, will only look at the picture step by step operation dilettante watch, that will be detailed detailed description of the basic concepts, step by step screenshot, easy-to-install comparison of the past. For example, use the ping command In the first class, if the network doesn't work, use the ping command to test if the network is open. The second type of writing: if the network doesn't work, in CMD mode, use the command format of ping X.X.X.X to test if the network is free. The third type of writing: if the network impassability, click start, select run, then type CMD in the run box, and then in the pop-up box, use the ping command format X.X.X.X, if according to the Reply from X.X.X.X bytes = 32 time = 3 TTL = 64 ms, is unobstructed, other display is not smooth.