1. What is the role of software configuration management? What does software configuration include?
– Software Configuration Management (SCM) is a technique for identifying, organizing, and controlling changes. Software configuration management applies to the entire software engineering process. Change is inevitable when software is built, and change exacerbates confusion among software developers on a project. The goals of the SCM activities are to identify changes, control changes, ensure that changes are implemented correctly, and report changes to other interested parties. From a certain point of view, SCM is a technology for identifying, organizing and controlling modifications, with the purpose of minimizing errors and improving production efficiency most effectively; – Software configuration includes the following: configuration
item identification, workspace management, version control, change control, status reporting, and configuration auditing.
2. Briefly describe c/s mode or b/s mode?
C/S mode: client/server mode. Working principle: Client submits a request to Server; Server uses some methods to process the request and returns the result to Client.
The B/S structure, that is, the Browser/Server (browser/server) structure, mainly utilizes the increasingly mature WWW browser technology, combined with various Script languages (VBScript, JavaScript...) and ActiveX technology of the browser, and uses a general-purpose browser to realize the powerful functions that originally required complicated special software and save development costs. It is a new software system construction technology.
3. Differences between web testing and app testing
In terms of system architecture:
web projects are generally b/s architecture, and browser-based
app projects are c/s, which must have a client, and users need to install the client.
As long as the web test updates the server side, the client side will be updated synchronously. App projects require both the client and the server to be updated.
In terms of performance:
web pages mainly focus on response time
, while apps also need to care about traffic, power, CPU, GPU, Memory, etc.
In terms of compatibility:
the web is based on browsers, so it is more inclined to be compatible with browsers, computer hardware, and computer systems.
App testing depends on resolution, screen size, operating system, and network.
Web testing is browser-based so there is no need to consider installation and uninstallation.
And the app is client-side, you must test the installation, update, and uninstallation. In addition to conventional installation, update, and uninstallation, abnormal scenarios should also be considered: including interruption during installation, weak network, and deletion of installation files after installation.
4. What is the key to a good test case?
White-box testing: Fewer use cases cover as many internal program logic results as possible.
Black-box testing: Fewer use cases cover module output and input interfaces. Find the most problems in a reasonable amount of time with the fewest use cases.
Consider both feasible and infeasible: (1) input (2) detailed operation steps (3) expected output (4) actual output
5. What is software quality?
In a nutshell, software quality is "the degree to which software conforms to explicitly and implicitly defined requirements". Specifically, software quality is the degree to which software conforms to explicitly stated functional and performance requirements, development standards explicitly described in documentation, and implicit characteristics that all professionally developed software should have. The main factors affecting software quality, these factors are the measurement of software quality from the management point of view. It can be divided into three groups, which respectively reflect the three viewpoints of users when using software products. Correctness, robustness, efficiency, integrity, usability, risk (product operation); understandability, maintainability, flexibility, testability (product modification); portability, reusability, interoperability (product transfer).
6. What is the difference between a client with 300 clients and 300 clients with 300 clients putting pressure on the server?
300 users on one client will occupy more resources of the client and affect the test results. Interference between threads may occur, resulting in some exceptions.
300 users on one client require more bandwidth.
For IP address issues, you may need to use IP Spoof to bypass the server's limit on the maximum number of connections to a single IP address.
All users are on one client, so there is no need to consider the issue of distributed management; while users are distributed on different clients, it is necessary to consider using the controller to deploy users on different clients as a whole. At the same time, you also need to give the corresponding permission configuration and firewall settings.
7. What is a test case, what is a test script, and what is the relationship between the two?
A specific set of input data, operation or various environmental settings and expected results provided to the system under test for the implementation of the test.
Test scripts are scripts written for automated testing.
The writing of test scripts must correspond to the corresponding test cases
8. What is the difference between a client with 300 clients and 300 clients with 300 clients putting pressure on the server?
300 users on one client will occupy more resources of the client and affect the test results. Interference between threads may occur, resulting in some exceptions.
300 users on one client require more bandwidth.
For IP address issues, you may need to use IP Spoof to bypass the server's limit on the maximum number of connections to a single IP address.
All users are on one client, so there is no need to consider the issue of distributed management; while users are distributed on different clients, it is necessary to consider using the controller to deploy users on different clients as a whole. At the same time, you also need to give the corresponding permission configuration and firewall settings
9. What is the reason for the website freeze?
Reason 1: Too many http requests.
Solution: Standardize the interface design and reduce the number of http requests.
Reason 2: The time to receive data is too long, such as the download resource is too large.
Solution: To compress HTTP transmission, gzip lossless compression can be used, and the compression effect is the best.
Reason 3: The JavaScript script is too large, blocking the loading of the page
Solution: Put the JavaScript script before the label. When the script does not have async and defer, the JS file will be executed immediately after downloading. In this case, putting the script at the top will block the rendering of the page, and it will cause a "white screen" when the network speed is slow, and the page will not continue to render until the script is downloaded. Therefore, placing script at the bottom allows the page to render as quickly as possible.
Reason 4: CSS, JavaScript, pictures, etc. need to be loaded repeatedly.
Solution: Static resources are placed on a static domain name to reduce the burden of repeatedly downloading static resources.
Reason five: impact of cookies
Solution: reduce the impact of cookies. Remove unnecessary cookies, or completely disable cookies if the page does not require them. In addition, reducing the size of the cookie and setting an appropriate cookie expiration time can also weaken the impact of the cookie.
Reason 6: Too many webpage resources
Solution: Use CDN to deploy the network to improve the download speed, and you can first distribute webpage resources through free CDN providers.
10. During the pressure test, the QPS has been unable to increase, how will you troubleshoot?
– Look at the performance of the server under test to see if the resources are full, causing the request to fail to connect.
Solution: expand the server under test.
– See if there is an error on the interface and whether the response time is slow
Solution: Interface performance optimization.
– Check the performance of the stress test machine to see if the network IO is full and the number of concurrency cannot be reached.
Solution: Multiple stress test machines run concurrently.
– See if the stress testing tool supports concurrent requests
Solution: Use multi-threading or coroutines to concurrently request
11. 10% of users report that the function cannot be used. How do you troubleshoot?
–APP version impact, it may be that interface changes do not consider version control, which affects users of lower versions;
–OS version, it may be that the user’s operating system is too high or too low, and there is no compatibility; –Gray testing or AB testing , it may be a functional defect
that affects some gray users ;
12. The APP prompts that the network cannot be connected, how will you troubleshoot?
Step 1: Check the network environment
Check whether 4G and Wifi are available, you can first check the status of the mobile network connection icon, whether there is a signal, whether the network is weak, and you can switch to other APPs to test whether the network is available.
Check whether there are network restrictions, such as apps that are only available on the company's intranet, and you cannot connect in other network environments.
Check whether the proxy is connected or whether the proxy connection is abnormal. After the mobile phone is connected to the computer proxy, if the certificate is not installed, the HTTPS request will be abnormal.
Step 2: Check the network request of the APP.
Capture packets, check whether the domain name requested by the APP is correct. Capture packets, check whether the backend interface responds with timeout
.
13. How to test the like function of WeChat?
Functional test
1. After a like, the number of likes will be +1, and the avatar of the liker will be displayed in the like blue. 2. After a like
, mutual friends should be able to see the liker in the like area. 3. After a like,
the non-common friends cannot see the liker in the like area.
6. For the first time to like, notify the user, cancel the like, and then like, do not notify the user. Whether you can comment normally before liking 15. Whether you can comment after liking 16. Repeated liking, cancel
liking , whether the
function is normal
APP test
1. Weak network test, whether the likes are updated in real time under weak network conditions
2. When there is interference (phone calls and text messages) when liking, whether the likes are displayed
3. Whether the power consumption and traffic are normal
Performance test
1. A large number of users concurrently like, the response time of the interface, the maximum qps
2. A large number of users concurrently like, at this time, the interface likes, whether the function is normal
Compatibility test
1. Different mobile phone models, oppo mobile version and Netcom
2. Different mobile phone versions, OPPO r7, r10 ios 7,8
3. Different systems, Android, iOS
UI test 1. According to the UI map , whether the
display position, color, icon, and font are displayed normally. 2.
When no like is displayed
, whether it is displayed in gray.