Introduction to test points:
Requirements analysis is to find out what functions users need and how users will use the system. In this way, when we test, we can know more clearly how the system should run, design test cases better, and test better.
Testing requirements analysis of the test plan - related questions and analysis content can be viewed by clicking on the link at the end of the article!
1. Test questions
1. There are three employees ABC, each employee has a task;
the task types are normal and difficult;
it is impossible for the three employees to have difficult tasks at the same time;
each employee does not know his or her task type, but he can know The mission types of the other two people;
A thought for a while and said, he didn’t know whether his own was normal or difficult;
B thought for a while and said, he didn’t know whether his was normal or difficult;
asked C if he could infer his own mission type. ,Why? Write down the reasoning process
Answer:
(1) It is impossible for three employees to have difficult tasks at the same time, which means that there is at least one ordinary task; (
2) A does not know the type of his own task. Combining (1), it can be concluded that BC is not all difficult tasks.. ....
2. A certain agricultural product information management and release system is a B/S system developed using JAVA EE architecture. The system performance requirements are as follows:
(1) The main function operations are completed within 5 seconds;
(2) Support 50 online users;
(3) The main functions of agricultural product information management support at least 20 concurrent users;
(4) Within 50 users During the peak period of concurrency, the processing capacity of the main function of agricultural product information management must reach at least 8trans/s;
(5) The system can run stably for 12 hours continuously.
The key indicators that should be tested in the system performance test are: ( )
A. Transaction execution response time indicator
B. Number of concurrent users indicator
C. Transaction execution throughput indicator
D. Number of concurrent processes indicator
The correct answer is A B/S system where users upload data to the server for processing...
3. What impressive bugs have you encountered? What are the reasons for bugs in interface testing?
Answer: The interviewer asks what impressive bugs he has encountered. In fact, he doesn't care whether the bug you describe is really valuable or how bizarre it is? He just: Understand your testing capabilities in your usual work...
2. Examination articles
1. Software testing requirements analysis method
To be precise, the so-called testing requirements are what needs to be tested in the project. In our testing activities, we first need to clarify the testing requirements (What) before we can decide how to test (How), the testing time (When), how many people are needed (Who), what the testing environment is (Where), and the skills required in the test. , tools and corresponding background knowledge, risks that may be encountered during testing, etc...
2. Software Testing - Requirements Analysis
Requirements are the beginning of software project development and the first collective discussion after the R&D team is established. It is also an important part of ensuring quality...
3. The video
equivalence class of test points is the most effective and direct theoretical point for testing positions.
Testing requirements analysis of the test plan - related questions and analytical content can be viewed by clicking on the link below:
Testing requirements analysis of the test plan - Mobile link
Testing requirements analysis of the test plan - PC link
