0. Record the impression of joining CDG at that time
I was mainly responsible for the system test of the internal operation platform. When I just joined the company, the boss gave me an iteration process document of the operation center project to familiarized me with the internal operation platform. I have a look, ah, as a software engineering student, agile development, double week iteration, or have some understanding of (although there is no actual used), then send me TRPD link, the inside is all of the requirements, I see, dizzy, itself has a lot of operating platform module, bosses write requirements and special succinct (can get the information of special less), Let me write a test case for a module, I:?? Where is it written? Where is it tested? What about test links??
Fortunately, I have thick skin, although the eldest brother looks very busy, I still have a question to ask, they also slowly familiar with and started, although the beginning of writing like primary school students write a composition, but still after the eldest brother’s teachings and their own intelligence gradually can enter the eye.
After working for a period of time, I did not touch a word of code, but I have more understanding of testing, for example, to see the problem really comprehensive, to carefully think about any situation that may happen, this ability is not all people have, instantly feel that the status of test engineer has risen again.
What is a test case?
A test case is a document that consists of preconditions, inputs, execution conditions, expected results, etc. to complete the test data for a specific requirement or target and reflect the test plan, method, technology and strategy. (In simple terms, it is a document of given conditions, execution process, and expected results for subsequent testers to test.) Test cases need to be designed to cover as many states of the software as possible, taking into account cycles.
2. Is it necessary to design use cases?
If you do not write it down, it is likely that the test point will be missed when it is executed. In addition, it is not convenient for use case review and use case summary, which will not greatly improve the later test work. So test cases must be written, granularity depends on the situation. For projects with few testers and tight online time, only mind mapping can be done to list test points.
3. Benefits of designing use cases?
The process of designing use cases allows for a deeper understanding of requirements and familiarity with each function point to ensure the full coverage of each test point as possible. It also facilitates use case review.
4. Do I have to write test cases?
For medium to large tasks, write detailed test cases; For small urgent tasks, you can write test points; Be sure to write test cases for new modules.
5. How to write test cases?
(1) Split test points according to requirements documents; (2) According to test case design method + experience + split test point + general use case constraints. To design the final detailed test cases; (3) The idea of writing use cases: product demand-test demand-test point-test cases; (4) Compatibility, browser compatibility and operating system compatibility should also be considered. If it is APP test, interruption test and weak network test should also be considered. Use cases should also be designed with the correct field values in the database involved; Need to pay attention to the use case design of the associated module; Pay attention to the design of use cases of new interfaces and new fields; (5) In addition to sorting out test points with XMind, we can also find the matching relationship between roles and function modules according to requirements documents, and output usecase diagram — output flow chart — output test cases according to business rules, USecase and flow chart.
6, Use cases must have 4 aspects?
Prerequisites, procedure, expected result, and test result; Use case points: Include coupling with other modules, level of use case (Level0, Level1), consideration of what requirements must be completed and what can be completed later.
7. Use case design philosophy?
First of all, the quality of products should be guaranteed. The number of test cases does not determine the quality. Comprehensive coverage should be achieved and high-quality automated testing should be advocated.
8. How to test and design test cases without requirements documentation?
A. Find other relevant documentation to help you understand what the product to be tested needs to accomplish; B. Attend as many meetings within the project team as possible, such as requirements discussion, design discussion, plan discussion, etc., to deepen the understanding of the product; C. Consult relevant personnel – project leader and marketing personnel; D. Convene relevant personnel to discuss the results you have sorted out. After passing the review, this document can be used as a basis for designing your case; E. If it is an online product, you can use the product more and ask the product manager if you don’t understand; F. You can also look at historical bugs to learn something that needs attention.
9. What are the design methods of test cases?
Equivalence classification method, boundary value analysis method, function graph method, error conjecture method, causal graph method, scene method, etc. 10. Write use cases, in what form and with what tools? A: Excel, Word, but also tools such as TestLink, Zentao, XMind. I usually use XMind to design test cases. For details, please refer to writing test cases using XMind.
I also just entered the small white ~ follow-up will continue to be more, progress together ~ refueling!