1. Design a use case for a login page
Functional test:
Correct input, empty input, character type verification, length verification, whether the password is encrypted and displayed, capital prompts, whether the jump page is successful, and after logging out Log in with another account
UI:
The interface layout is reasonable, the style is unified, the interface text is concise and easy to understand, and there are no typos
Performance Test:
How many seconds does it take to open the login page, how many seconds does it take to click login to jump to the homepage, multiple clicks, multiple clicks
Security:
Whether the user name and password are encrypted and sent to the server, the limit on the number of incorrect logins (to prevent brute force cracking), multiple users logging in to one machine, multiple logins for one user, and checking whether the password can be seen in the element< a i=8> Compatibility test: Can different browsers, different platforms (Windows, Mac), and mobile devices work? Ease of use: a> Whether the input box can be switched by tab key, whether pressing Enter can log in, etc.
2. Introduce the test case design method (use case design method & test method need to be clearly distinguished)
Black box test case design:
Equivalence class division method,
Boundary value analysis method,
Error Speculation method,
Cause-and-effect diagram method,
Orthogonal test analysis method,
Process analysis method (scenario method), a> decision coverage, path coverage decision/condition coverage, condition combination coverage, condition coverage, statement coverage, White box testing:
Decision table method
3. You said the original recharge function, how did you test it?
1. First, let’s test the main function of recharge to see if the recharge can be successful;
(Equivalence class, boundary value, decision table, process analysis method, state transition method, error speculation method, exception handling method to test)
(1) Use boundary value Method to test whether the recharge limit can be successfully recharged
(2) Use special characters to enter the recharge input box to see if there is a prompt message
(3) Recharge input box Is there a prompt when clicking Recharge when it is empty?
(4) Enter the amount in the input box, then go back to the web page and then enter the recharge page. Is the entered amount still saved?
(5) Can the recharge be successful after going back and forth to the recharge interface multiple times?
(6) Can the recharge be successful if multiple recharge payment methods are selected?
(7) Select whether the online banking recharge of each bank can be successful
(8) When the recharge is successful, are there any relevant prompts and whether the page jumps correctly
(9) After the recharge is successful , whether the associated amount is displayed correctly
(10) After the recharge is successful, check whether the relevant data in the database exists and is correct
(11) Click on third-party payment (Such as Alipay, WeChat) Is there any relevant link page jump
(12) Can multiple payment methods be selected for recharge at the same time
(13) Cross selection After the payment method, select one of the payment methods to see if the recharge can be successful
(14) If the recharge amount is modified multiple times in the recharge input box, can the recharge be correct?
2. Let's test the recharge performance and use jmeter to simulate a large number of users recharging at the same time to see if the recharge can be successful;
3. Let’s test the security of the recharge
(1) Whether the recharge of bound bank cards and unbound bank cards can be successful;
(2) Binding of multiple bank cards with the same name and the binding of multiple bank cards by one user Can banks with different names be bound to recharge successfully
(3) Can recharge be successful with real-name authentication and without real-name authentication;
(4) Use boundary values Method to test the daily recharge limit, the number of times
(5) Test the maximum number of incorrect passwords that can be entered in a day, how many times the card is locked, and whether it is necessary
Go to the bank to unlock before recharging
(6) How many times do you need to enter the password after entering the recharge amount, whether it is encrypted, and whether the recharge can be successful without entering the password;
(7) Whether the recharge can be successful using other payment methods;
(8) Test the type of recharge amount;
(9) The amount of money recharged after the recharge Whether the balance of your account and the platform has increased;
(10) Whether a single click or multiple clicks will result in successful recharge; and whether multiple clicks will result in multiple recharges; 4. We also It is necessary to test compatibility to see if different versions, resolutions, and different browsers can charge normally (14) Cross-site attack, data leakage; (13) Whether the recharge can be successful if you do not choose a bank card or other payment method; (12) Whether the recharge is successful without logging in as a user;
(11) Whether the recharge is successful when multiple recharge interfaces are opened at the same time;
value;
5. Test the usability to see if the entire recharge process is easy to use. If you encounter something you don’t understand, is there any corresponding warm reminder?
;
6. We will also consider testing abnormal situations: (network abnormalities and equipment abnormalities), for example:
(1) During the recharge process, there is suddenly no network or the network is interrupted or the recharge is successful.
(2) The power suddenly goes out during the recharge process. Can the recharge be successful? Successful;
(3) The device freezes during the recharge process. Can the recharge be successful?
(4) The bank card is reported lost, canceled, and the balance in the card is insufficient. If the amount is frozen and the amount exceeds the limit, can
recharge successfully;
7. Let’s test the interface again:
(1) Whether the interface is beautiful, the format is correct, and whether there are typos in Chinese;
(2) Can our recharge interface be opened in other browsers and can it be displayed normally? Normal recharge;
(3) Whether the buttons on the interface conform to the user's usage habits, whether the main and key function buttons are easy to find, and whether the operation is convenient;
(4 ) After the interface is zoomed in different browsers, whether the interface layout is displayed normally
4. How to test a paper cup?
Functionality: Make sure there are no leaks when filling the cup with water; whether the water can be drunk
Safety: Does the cup contain poison or bacteria?
Reliability: The degree of damage to the cup when dropped from different heights
Portability: Whether the cup can be used normally in different places, temperatures, etc.
Compatibility : Whether the cup can hold juice, plain water, alcohol, gasoline, etc.
Ease of use: whether the cup is hot to the touch, has anti-slip measures, and is convenient for drinking
User documentation: Does the user manual have a detailed description of the usage, restrictions, conditions of use, etc. of the cup?
Fatigue test: Fill the cup with water (Case 1) and leave it for 24 hours to check the leakage time and situation; fill it with gasoline (Case 1) Case 2) Leave it for 24 hours to check the leakage time and situation, etc.
Pressure test: Use a needle and continuously add weight to the needle to see how much pressure it will penetrate
5. How to test a website for you?
1. First, look for relevant documents such as requirement descriptions and website design, and analyze test requirements.
2. Develop a test plan, determine the test scope and test strategy, generally including: functional testing, interface testing, performance testing, database testing, security testing, compatibility testing< a i=2> 3. Design test cases: Functions can include, but are not limited to, the following aspects: Link testing. Whether the link jumps correctly, whether there are empty pages and invalid pages, whether there are incorrect error messages returned Test of the submission function Whether the multimedia elements can be loaded correctly and display Whether multi-language support can correctly display the selected language Interface testing can include but is not limited to the following aspects: Whether the page has a unified style and beautiful appearance Whether the page layout is reasonable, and whether key and hot content are highlighted Whether the controls are used normally For necessary but not installed controls, is there an automatic download and installation function? Performance test: Stress test, load test Database testing should specifically determine whether it needs to be carried out: Consider connectivity, database storage operations, verification of data content, etc. Security testing:< /span> Database compatibility Software platform compatibility Operating system Compatibility Browser compatibility Compatibility testing, determine the supported platform combinations based on the content of the requirement description Common security issues related to development languages Checks for things like SQL injection, cross-site attacks. Whether there is an overflow, leading to system crash or permission leakage Check the basic login function
4. Carry out testing and record defects
Reasonably arrange and adjust the testing progress, obtain the resources required for testing in advance, and establish a management system (requirement changes, risks, configurations, test documents , defect reports, human resources, etc.)
5. Regularly review, evaluate and summarize the test, and adjust the content of the test
6. How to comprehensively test a product? Take the SMS function of a mobile phone as an example to illustrate. The SMS function that comes with a mobile phone is not software such as WeChat or QQ.
Can open or close the text message interface normally
Text messages can be edited, modified, and deleted normally
Text messages can be sent and received normally
The font and color of the text message page are displayed normally
The text message font is adjustable
Send text messages to multiple people at the same time
To a special number Send text message
Operator
Non-existent mobile phone number
Service number (charged, non-charged)
Receive verification code
SMS power consumption test
SMS with and without Internet connection
SMS interference test< /span> Hide to the background, perform other operations, and then come back
While editing the text message, make a call
7. WeChat Moments like test?
1. Function test
Whether WeChat friends can like and cancel likes
Whether I can support likes and cancellations when I post a message a> Multiple users have liked it. If you open the Moments again, can you see who has liked me in order? Like After that, exit the page and enter the Moments again to see if the like message still exists Can you comment after liking it? Can you click and like the WeChat nickname to jump to the user's homepage Whether the likes are displayed Name Whether the order of multiple likes is arranged in chronological order
What will happen if you like multiple times? Whether the same friend receives prompt information after liking it Whether the prompt information from the same friend is in chronological order Whether the WeChat nickname will be displayed on likes from the same friends 3. Compatibility test Whether likes and cancellations can be performed on both the computer and mobile phones Like function Whether different mobile terminals can like and cancel the like function (including Apple, Android) 4. Usability test What happens when the network is weak? Is it possible to like when the network is disconnected? Users can view it after a few seconds after clicking like When the like is successful, the same applies to canceling it When multiple users like me at the same time, can I receive prompt messages from all of them 5. Security test a> Will likes leak relevant information about WeChat users
8.How to test WeChat red envelopes?
9. If JD.com has a shopping page for you, how would you test it? What key features are tested?
First conduct needs analysis, use xmind to sort out the test points, and then write cases. After that, conduct case reviews and seek opinions from others. Afterwards, the case will be improved and sent out for others to check.
The test point is the UI aspect first: testing on aesthetics, ease of operation, and ease of understanding.
Then consider its function points, register and log in, add shopping cart, place an order, pay, ship, confirm receipt, and evaluate.
There is also the binding of bank cards and real-name authentication when paying.
Performance: response time for opening web pages, confirming orders, making payments, etc.
Compatibility: Supports various mainstream browsers, ie, 360, Firefox, Google, etc.
10. Regarding the test point of adding a shopping cart, tell me how you want to test "add a shopping cart" (from the perspective of adding, deleting, modifying, and checking)
1 Can be added to the shopping cart, and can the same item be added to the shopping cart again.
2 The upper limit of the number of items in the shopping cart (Taobao limit is 100 items)
3 Whether the items can be removed from the shopping cart normally, and whether the items can be removed again. Add it back.
4 Whether the quantity of each added product can be increased or decreased normally, and the quantity is greater than 0
5 Exit the shopping cart and check the shopping cart again. The products are normal.
6 You can select all the products in the shopping cart, cancel the selection of all, and make multiple selections. The selected products and quantities can be ordered normally.
7 After the product was added to the shopping cart, it was removed from the shelves. The shopping cart will prompt that this product has expired.
8 After the product is added to the shopping cart, if the price is reduced, the shopping cart will have a price reduction prompt.
9 After adding the product to the shopping cart, the stock is out of stock.
11. How to test online bank transfer? Design a test case.
From a macro perspective, we can consider it from the quality model (universal formula), focusing on testing the function, performance and security of the transfer.
When designing test cases, you can mainly use the scenario method. First, list the basic flow and alternative flow of transfer. Then design the scenario, and finally design the data based on the scenario.
1 Check the ui interface first.
2 Test the function again:
2.1 Verify peer transfer and inter-bank transfer.
2.2 Verify transfer limit.
2.3 Verify transfers from illegal accounts (reported lost, frozen, locked accounts).
3 Test the performance again.
12. I give you an app, how to test it (app test case?)
01 Interface
Test whether the interface is consistent with the original interface image in the requirements document,
use different mobile phone interface resolutions, and interface size, etc. Test
02 Function
Except for installation, uninstallation, update is similar to the web version
03 Compatibility
System compatible (ios, Android)
Model compatible (iPhone, Huawei, Xiaomi, Samsung, vivo, OPPO)
Resolution compatible SQL statement injection Cannot enter the interface directly The backend cannot be accessed through the url connection bracket The front desk cannot access the backend 10 Permissions 2G, 3G, 4G, China Mobile, China Telecom, China Unicom, and switching between networks, use fiddler to perform weak network Test 09 Network test Monitor the CPU , memory, fps, etc. Emmagee goes to test the performance of the APP 08 Performance test Is it convenient for users to use? 07 Ease of use Permission test Important data encryption xss script attack 06 Security Whether the interface is the original interface, whether the input data is saved, and interactive testing with other apps Volume adjustment , lock screen, rotate, return key, main menu key, screenshot, alarm clock, standby, plug and unplug data cable, headset, wifi, Bluetooth, phone, text message, low battery, check whether the function is in normal use, Interactive use with the phone’s inherent function modules 05 Interactivity Check the software for a long time Will there be a crash when running? 04 Stability The software itself is forward and backward compatible
System version compatibility
13, AMT Terms and Conditions
Requirements specification:
After inserting the card, enter the correct password and proceed with the withdrawal operation. After the withdrawal is successful, print the receipt and return the card to complete the withdrawal process.
After inserting the card, if the card is invalid or the account number does not exist, the card withdrawal process ends;
The number of incorrect password entries must not exceed 3 times, otherwise a prompt will be given and the card will be refunded, ending the process;
After inserting the card, the account number and password are successfully verified. After selecting the withdrawal operation, the ATM is out of cash, and the process of returning the card ends;
In the following 3 situations, you need to re-enter the withdrawal amount after being prompted:
Withdrawal amount > Account balance;
Withdrawal amount > ATM balance;
Withdrawal amount > Withdrawal amount.
Please use the scenario method to designtest cases.
1. First, obtain the basic flow and alternative flows according to the requirements specifications:
2. Organize the basic flow and alternative flow of the program:
Basic flow: that is, the scenario under normal circumstances. This question should be about inserting the card, entering the correct password, successfully withdrawing money and Print the receipt and get the card.
Alternative flow: It is some abnormal situations, such as incorrect password, invalid card, etc.
To put it simply, the basic flow can achieve the goal, but the alternative flow cannot achieve the final goal.
3. Generate scenarios based on basic flows and alternative flows
4. Generate test case corresponding scenarios
14, Input 3 integers, output equilateral triangle, right triangle, isosceles triangle, ordinary triangle test case?
14. How to design use cases for file download?
Function
Supports downloading of the current page, or opening and saving in a new window.
Compare the file after downloading to see if it is completely consistent with the file when uploaded.
Pay attention to whether the file name is empty, contains special characters, or has a long file name, and whether the downloaded file is consistent with the uploaded file.
The network is interrupted during the file downloading process. Wait for the network to recover to see if the file can continue to be downloaded.
Whether the downloaded file supports multiple files to be downloaded at the same time, or the same file to be downloaded multiple times?
If the server is abnormal during the download process (disconnection, etc.), whether to continue when the server returns to normal Download
Whether to pop up the download page pop-up window when clicking the download button
After the download is completed, check the file name, file size, file format, and download start time in the server log and database. , download end time, etc. are consistent with the response data of the front-end packet capture interface
Download file abnormality test, such as insufficient local disk space
File storage
After the file is uploaded to the server, is the file storage NAS or object storage OSS used?
After the file is uploaded to the server, are there any Disaster recovery backup
Security issues
After the file is uploaded to the server, whether the file name is encrypted
Whether users without access rights can access
Whether users who do not have download permission can download
Performance
Jump to the download page response time
Pop up the save window page response time
Single user download File rate, whether it meets the demand target.
Whether the speed at which multiple users can concurrently download files meets the required target
The time it takes to complete the download
15. How to test the search box?
- function test
- The search content is empty, how does the verification system handle it?
- If the search content is a space, check how the system handles it.
- Boundary value validation: Verify the system's processing inside and outside the allowed string length
- When inputting an extremely long string, will the system intercept the allowed length to check the result?
- After the legal string length, add a space to verify the search results.
- Add spaces, commas, and tabs between multiple keywords to verify whether the system’s results are correct.
- Verify each legal input to see if the result is correct
- Whether to support copying, pasting, editing and other operations of search content
- Whether to support enter key search
- Enter the same content multiple times to see if the system’s search results are consistent.
- Special characters, escape characters, html scripts, etc. need to be processed
- Sensitive words, prompting users to have no permission, etc.
- Whether the input content supports shortcut key operations, etc.
- Only allowed string lengths etc. can be entered
- Whether the input link jumps correctly
- Is the search history shown below?
- Is there an association function for searching content?
- Is it possible to enter numbers, English, Chinese?
- Is it possible to mix input numbers in English and Chinese?
- You can also search by entering pinyin
- Does the content of the voice search match?
- Unable to search when the network is disconnected
- When searching for pictures, you can choose to take a photo or select a picture from the album to search.
- If you select a picture from the photo album to search, is there a limit to the size of the picture? What is the maximum size?
- There is a camera picture next to the search box to facilitate image search.
- Click Clear History. Will the search box clear the history?
- Can you identify the content in the picture?
- Click Search to display the search interface
- Interface testing
- Check whether the UI is displayed correctly and whether the layout is reasonable
- Are there any typos?
- Is the layout of the search results displayed beautiful?
- The color of the viewed result link should be grayed out.
- When the number of results is huge, is the paging layout of the page reasonable?
- Is the color matching of the interface reasonable?
- Security testing
- Script disabling
- SQL injection, retrieval of SQL SELECT statements, etc.
- Retrieval of sensitive content is prohibited
- Search for special characters
- Deleted, encrypted, and authorized data are not allowed to be discovered. 6. Are there security design controls?
- Compatibility testing
- Multi-platform Windows, mac
- Mobile platform android, ios
- Multi-browser Firefox, chrome, IE, etc.
- Performance Testing
- Search page link opening speed time
- Search results take time
- Search response time when network is weak
- Response time when searching under different network speeds 3g, 4g, WIFI
- Ease of use
- Has association function
- How well the search content matches the search results
- Support photo search and voice search
15. How to test elevator/umbrella/cup/pen/A4 paper/paper cup?
How to analyze
Let’s take a trolley case as an example:
1. So first of all, you should ask the interviewer, what are the needs, such as what kind of trolley case and size are you testing? Material? brand?
2. If the answer is no, then your next idea is: there is no requirement document, but I understand the basic business functions of the trolley case. Based on this, I will analyze from the following aspects:
Functional testing (single function, logical business/functional interaction), interface testing, usability testing, compatibility testing, security testing, performance testing
Specific case analysis
——Functional test——
->Whether the size of the trolley case, the thickness of the case, the capacity, the load-bearing capacity of each surface (including the trolley surface, the caster surface), and the trolley load-bearing capacity meet the quality inspection standards
->The trolley box exceeds the capacity, each surface (including the trolley surface, the caster surface) exceeds the load-bearing capacity, and the trolley exceeds the load-bearing capacity. Is it normal use?
-> Whether the telescopic rod is normal, and whether it is flexible to expand and retract. -> Whether the wheel is rolling normally, whether it is one-way or 360-degree rotation
-> Whether the lock of the box is normal and whether unlocking is convenient and safe
——Interface Test——
-> Whether the material, color, pattern, and shape of the box fabric meet the requirements, and whether the color is easy to fall off
->Whether the material, color, length of the box tie rods, and the material, color, and size of the box casters meet the requirements?
-> Whether the box tag logo is correct and whether the auxiliary instructions are correct
——Usability test——
-> Whether the handle of the box trolley is easy to hold and non-slip, and whether the side handle is easy to hold and non-slip
-> Whether the zipper for opening and closing the box is easy to drag and whether the casters are flexible
——Compatibility Test——
->Whether the box casters can be used on flat floors, sand, dirt, and stairs
->Whether the box can be used normally at different temperatures, such as high temperature, low temperature, and ultra-low temperature
->Whether the box can be used normally in rainy, snowy or hailing days
——Security Test——
-> Whether the material of the box fabric is safe and non-toxic; whether it releases harmful substances when exposed to high temperatures or rain
-> Whether the corners of the box are smooth and without edges
->Whether the box handles and side handles are smooth
——Pressure performance test——
-> After carrying the load for 30 kilometers continuously, check whether the trolley caster box is normal and has no wear.
-> Load the load and unfold the pull rod, lift the handle of the pull rod so that the box is in a suspended state, vibrate left and right 500 times, check whether the pull rod is normal
-> The load is dropped from about 1 meter, and each surface (including the tie rod surface and caster surface) is dropped to the ground 5 times. Is it normal and without wear?
-> After loading, roll the entire box 360 degrees 30 times to see if it is normal and has no wear.
-> After loading, in the next 25 stages, check whether the surface of the caster rod box is normal and free of wear.
-> Expand and retract the pull rod back and forth, repeat 1000 times, check whether the pull rod is normal
If you encounter this type of question in the future, no matter what, you can reply to the interviewer like this: I don’t know the specific requirements, but I understand the use of basic functions, so I will analyze it from the following aspects. First of all, If you think about functional testing, balabla; if you think about interface, balabla,..., if you think about stress testing, balabla; the above is my answer, thank you for answering like this, it will appear very organized, and each different testing direction can be used on the spot. , what are you afraid of, it’s a divergent thinking question anyway, you can say as much as you can think of ~
16. Test cases for login interface:
1. Interface UI test:
① Whether the layout meets the requirements of the requirements document;
② Whether the length and height of the input box and button meet the requirements ;
③Whether the design style of the interface is consistent with that of the UI;
④Whether the text in the interface is concise and easy to understand, with no typos.
- Functional test:
①Enter the correct user name and password to verify that the login is successful;
②The user name and password are empty, the verification login fails and the Prompt message;
③After successful login, whether to jump to the corresponding interface;
④If the user name and password are too long or too short, whether there is a prompt message; a> ⑥ After failed login, there is no function to remember the password; ⑩ Enter the wrong user name and password and check the prompt message. ⑨ Enter the password and open the uppercase keyboard to see if there is a prompt message; ⑧ Whether the registration, forgotten password, logout, etc. login links on the login page are correct. ⑦ Whether the password is encrypted and displayed;
⑤ There are spaces, special characters or other non-English characters between the user name and password; - Performance test:
①It takes a few seconds (duration) to open the login interface;
②Enter the correct user name and password to log in successfully, login duration No more than 5s. - Compatibility test:
① Whether the mainstream browser displays successfully;
② Whether different platforms display successfully;
③Whether the display is successful on mobile devices (Android iOS);
④Different resolutions; - Usability test:
①Whether full keyboard operation is supported and whether there are shortcut keys;
②Enter the user name and password and press Enter to see if you can log in ;
③Whether the input box can be switched with the tab key. - Security test:
① Whether the user name and password are sent to the web server in encrypted form;
② The input of user name and password should be blocked SQL injection (refers to the web application not judging the legality of the data input by the user or filtering it strictly, and obtaining the corresponding data information; the methods include: numeric injection, character injection and other injections, such as cookie injection, post Injection);
③ The input of user name and password should be prohibited from entering scripts (executable files written according to a certain format);
④ Limitation of the number of incorrect logins ;
⑤Consider whether to support the login of multiple users on the same machine;
⑥Consider the login of one user on a polymorphic machine.
17. Testing a game in King of Kings:
For example, Arthur:
①Can skills be used and whether basic attacks can be used normally?
②Can he equip and sell
Can you change skins and buy new skins?
④Whether Arthur’s mantras are expressed smoothly and emotionally;
⑤The effective duration of each skill;
⑥Whether he can operate it himself when not operating;
⑦The flash, end or punishment, Verify whether weakening and other functions are used normally;
⑧Whether the blood recovery skills can be used;
⑨Whether operations such as launching an attack and retreat can be carried out;
⑩Can shortcuts be implemented;
18. WeChat red envelope test case
Single red envelope:
1. The red envelope amount is empty, 0, 0.01, 200.00, 200.01, 199.99, 200
2. Enter numbers, letters, Chinese characters, and special characters when leaving a message
3. Message length
4. Copy and paste the message
5. Select expressions to collect expressions and other expressions
6. Delete emoticons and reselect emoticons
7. Select the payment method: change, bank card, add new card payment. Among them, the number of money <The number of red envelopes, Among them, the number of money=The number of red envelopes, Among them, the number of money>The number of red envelopes
8. Use fingerprint to confirm payment (correct, wrong fingerprint)
9. Use password to confirm payment (correct, wrong password)
10. After the red envelope is successfully sent, the amount of money in the corresponding payment method is reduced (the reduction amount is consistent with the amount of the red envelope)
11. The recipient can see the specific information of the red envelope, and the amount, message, and emoticon of the red envelope can be displayed correctly.
12. After the red envelope is opened, it will show that it has been received, and the correct amount will be added to the recipient's change. You can only view the red envelope information when you receive it again.
13. The person who sends the red envelope receives the red envelope himself.
14. If the red envelope is not received for 24 hours, it will be returned. The amount of money in the corresponding payment method will increase (the increase amount is consistent with the amount of the red envelope), and the other party cannot receive the red envelope.
Group red envelopes-ordinary red envelopes: (only the differences from a single red envelope are written)
1. The number of red envelopes is empty, 0, 001, 100, 99, 101
2. When the red envelope is opened, each amount is the same. It is the amount corresponding to the single amount set when sending the red envelope.
3. When the red envelope is opened, there will be corresponding prompts.
4. The person who sends the red envelope receives the red envelope himself
5. If the red envelope is not opened within 24 hours, the remaining money will be returned and the amount of money in the corresponding payment method will increase.
Group red envelopes - lucky red envelopes:
1. Total amount of red envelopes/number of red envelopes<0.01
2. The amount of red envelopes opened by each person is different, and the total amount is consistent with the total amount set for red envelopes.
3. The best luck will be shown after the red envelope is opened within 24 hours.
4. If the red envelope is not opened within 24 hours, it will not show the best luck.
Compatibility: Android, Apple, different models and versions of mobile phones
UI test: There are no typos in the interface and the style is unified.
Interruption test: switching between different applications, disconnection, incoming calls, text messages, low battery, and no battery on the phone
Network test: 2g/3g/4g WiFi, China Mobile, China Unicom, Telecom, weak network, no network
19. WeChat Moments test case
function test
1. Moments sending function
1) Just send text
a. Consider the text length: 1-1500 characters (the data is Baidu data), exceeding the maximum character length
b. Does the text support copy and paste?
c. Null verification
2) Only send pictures
a. Local photo album selection/shooting
b. Picture quantity verification: 1-9 pictures, more than 9 pictures
c. Null verification
3) Only send videos
a. Local photo album selection/shooting
b. Video seconds verification: 1-10s, exceeding 10s
c. Video number verification: 1, more than 1
d. Video format verification: supported video formats, such as mp4, unsupported video formats
e. Video size verification: within 400kb for Apple, 200-300kb for Android (this is Baidu data), exceeding the specified size
f. Video preview addition, deletion and modification operations
g. Null verification
4) Send text + picture: Enter the text and picture that meet the requirements for verification.
5) Send text + video: Enter text and video that meet the requirements for verification.
6) Sending pictures + videos: sending is not supported
7) Are there any restrictions on content sent to Moments, such as pornography, gambling, drugs and other sensitive words?
8) Location
a. Do not display the location: Send to Moments without displaying the location
b. Select the corresponding location: search support, automatic positioning, manual editing
C. Click Cancel and return to the previous page.
9) Who can watch
a. Set public: visible to all friends
b. Set private (visible only to you): View your Moments - visible, friends view Moments - invisible
c. Set partial visibility (visible to some friends): selected friends - visible, unselected friends - invisible, whether there is a maximum number of people
d. Set who not to see (selected friends are invisible): unselected friends - visible, selected friends - invisible, whether there is an upper limit on the number of people
e. Click Cancel and return to the sending page.
10) Remind who to watch
a. Remind a single person/remind multiple people: friends who are reminded-receive message reminders, friends who are not reminded-no message reminders
b. Is there a maximum number of people?
c. Click Cancel and return to the sending page.
11) Synchronize QQ space: not synchronized by default, synchronized to QQ space
12) Cancel the operation of sending to Moments
a. Select the camera, click Cancel, and return to the Moments page.
b. Enter the Moments sending page, select the text image, and click Cancel.
13) Is there an upper limit on the number of times the Moments can be sent in a day?
2. Moments browsing function
1) Text viewing:
a. Whether the text content that is too long is hidden, and supports viewing of the full text
b. Right-click and select Copy, Collection, Translate
c. Does the url link support clicking to jump to the web page?
2) Picture viewing
a. Right-click on the thumbnail to support collection/editing
b. Click to support large image browsing
c. Choose to send to friends, collect, save pictures, and edit.
d. Multiple pictures support left and right sliding browsing.
3) Video viewing
a. Right-click the video to support mute play/collection
b. Click the video play button to support video playback
c. Choose to send to friends, favorite, save video, and edit.
4) Sharing dynamic browsing: Whether the circle of friends is displayed normally after sharing in QQ space/public account articles/non-Tencent products
5) Like: like, unlike
6) Comments
a. Comment length: The number of words in the comment is reasonable, and the comment exceeds the upper limit of the number of words.
b. Comment type: pure Chinese, pure numbers, pure letters, pure characters, pure emoticons (WeChat emoticons/mobile phone built-in emoticons), mixed types, including url links;
c. Does the comment support copy and paste?
d. Null verification
e. Delete after posting a comment
f. Comment reply operation
7) Delete Moments updates
8) Change album cover
9) Is the refresh normal to obtain new updates?
10) Whether to slide up to load more
Interface/usability testing
1. Technical staff’s perspective: Is the page layout design consistent with the product prototype/UI renderings?
2. But in addition to considering 1, we must also consider the user's use: whether the function operation is easy, whether the page layout and typesetting style are beautiful and reasonable, and whether the prompt information is easy to understand.
Interrupt test
1. Main considerations: a) Core functions b) Current functions include real-time data exchange. For example, if posting to Moments or browsing Moments is interrupted, is it prone to crashing?
2. Interruptions include: switching between front and back, lock screen and unlock, network disconnection and reconnection, app switching, interruption of incoming calls/text messages, plugging and unplugging headphone cables/data cables
Network test
1. Testing of different network standards of three major operators
2. Network switching test: WIFI/4G/3G/2G
3. Test without network: For data cached locally, whether some circle of friends information supports browsing
4. Weak network test:
a. Delay: whether the page response time is acceptable, whether different network standards distinguish the timeout length, and whether a request timeout occurs and whether a corresponding prompt is given.
b. Packet loss: Is there a timeout reconnection mechanism? If there is no response, is there a corresponding prompt?
c. Integrity verification of page rendering
Compatibility testing
1. Whether the functional interface display of Android mobile phone, Apple mobile phone and pad version (mainstream) is normal
2. Is the data displayed in Moments on each platform consistent?
Safety test
When sending to Moments, does the text input script code cause any exception?
Performance Testing
1. Server performance test
It can be implemented through the loadrunner/jmeter tool, mainly focusing on TPS, response time, throughput, CPU, memory, etc.
2. App client performance test
It can be achieved through the GT tool. When running, pay attention to the occupancy rate of CPU, memory, traffic, power, etc.
20. Test case design for WeChat Moments like function
21. How to stress test the chicken game
1. Game server hardware
Hard disk I/o, memory, CPU
2. Network pressure
a. Long connection
Maximum number of connections, traffic (internal network, external network, incoming and outgoing) Number of connections established per second, actual processing capacity< /span>
b. Long connection and short cycle (similar to Http TCP applications, this is a special requirement, specifically for LoginAgent)
3. Database
Number of transactions per second, number of lock waits per second, average delay (ms), temporary CPU usage
4. The optimal number of threads for multi-threading
Multi-threading and multi-connection processing performed by the database
2. Windows Server environment testing method
1. Server performance monitoring
Use the performance monitor that comes with the Server to set the monitoring parameters of each process. This automatic tool of Windows is quite powerful. Everyone can basically use it by touching it. Each parameter is described in detail.
2. Notes on case design
a. For database performance testing, now all game server architectures have a process in front of the DB that implements the DB buffering function to reduce Frequent read and write operations on the database. So in fact, the database read is a lightweight quantity; the database write operation is a periodic performance process. The case design must be able to drive this cyclical performance process. For example, the battles in our game lead to changes in game player data, or drive the periodic storage of all online player data.
b. Select representative and most frequent game operations. Used to collect various performance indicators of the highest online users. For example, shooting, picking up props, using props, moving, chatting
c. Chat performance test
Broadcast chat is the function that most tests the game's information sending capabilities. By performing a global broadcast stress test. We can get the maximum load capacity of the server process sending information to the client. In turn, an estimate and frequency limit can be made for our various broadcast functions.
d. Mobile test of players on the same screen
Mobile + broadcast. These two types of information basically account for about 70-80% of online game traffic. The number of players on the same screen will increase the broadcast requirements for various data, which will greatly affect game performance. Therefore, mobile testing on the same screen is also a necessary part of broadcast testing. Appropriate optimization needs to be done based on actual results.
e. Testing with a large number of players logging in at the same time
When players log in, a large amount of information needs to be allocated and initialized; at the same time, a large amount of data needs to be downloaded to the client. The server requires a large number of TCP connection establishments. So it is a relatively critical process. This test case is a rather special one, but one that operations will definitely encounter.
f. Since the thread pool processes transactions, as the transaction takes time, there is a problem of the optimal number of threads. Too many threads will reduce server efficiency
3. Detailed issues
a. Testing requires careful consideration of the possibility that client performance affects the final performance of the server. For example
a1. The performance of the simulated client cannot effectively process the information returned by the server, which may cause the information sent by the server to be cached in the server system cache, thus showing that the server memory is constantly increasing. It manifests as insufficient sending capability of the server. In fact, it may simply be a performance problem on the client
a2. Client performance problems result in too few requests being initiated, resulting in too few requests processed by the server per unit time. . It manifests as insufficient server performance, but in fact it is simply due to insufficient client request capabilities.
b. Network bandwidth leads to insufficient final performance.
b1. Confirm each network card of the server and the mutual bandwidth. Otherwise, the server may delay processing client requests due to mutual bandwidth. The server is stuck
b2. The client simulates multiple players, such as 1,000 players. The client's network card or the bandwidth of the transfer server between the client and the server is too small, causing the server data to be unable to be sent and the memory to continue to increase. It appears that the server's sending capacity is insufficient, but it is actually an intermediate bandwidth problem.
c. Debug i/o leads to server performance degradation
c1. When performing performance testing, be sure to cancel the synchronous i/o used for debugging. For example, our server debuginternalLog. Synchronous I/O greatly affects performance, especially under stress testing, which may result in thousands or even hundreds of thousands of executions per second. A single file write operation can turn hundreds of thousands of processing capabilities into thousands of processing capabilities.
c2. The client avoids blocking operations, which results in a degradation in simulated multi-user performance, resulting in a degradation in server performance
d. Traffic needs to be differentiated into intranets
Internal and external network traffic are completely separated when the game is officially running. The prices are also completely different. A thousand Mbit external network is an unimaginable operating cost, but kmbps/s is now an acceptable price. The game process requires the configuration and binding of different network cards. Determine the internal and external network traffic.
22. How to test Taobao search box
1. Functional testing
- Enter keywords and check: whether the returned results are accurate. The length of the returned text needs to be limited
1.1 Enter the normal keywords, words, and sentences that can find the results, and the retrieved content , link correctness;
1.2 Enter keywords, words, and sentences that cannot be found;
1.3 Enter some special content, such as empty space, special characters, Punctuation marks, limit values, etc., methods of equivalence class division can be introduced; - The results show: title, seller, sales volume, single line/multiple lines, whether there are pictures
- Result sorting: price, sales volume, evaluation, comprehensive
4. When the returned results are huge, limit the actual amount of the first page and need to support page turning - Multi-option search: keyword brand place of origin price range whether to buy on Tmall or not to buy nationwide
- Whether it supports fuzzy search and wildcard query
7. Search when the network speed is slow - When the search results are empty
- Search when not logged in and logged in (the keywords/search habits searched by the user are stored when logged in)
2. Performance test:
1 Stress test: Performance under the pressure of different number of users (evaluation indicators such as response time, etc.)
2 Load test: See how many users the limit can carry at the same time and used normally
3 Stability test: How long can it continue to operate stably under normal pressure
4 Memory test: Is there any memory leakage
5 Large amount of data Test: For example, simulate searching results from huge amounts of data, or search for massive results and then list them to see how they perform, etc.
3. Ease of use: Is the design of the interactive interface convenient and easy to use?
1. There will be relevant humanized prompts based on different query results. Will you tell me then? When found, count the number and inform you? When there is a suspected input condition error, prompt possible correct input items, etc.;
2. The query results are listed in an orderly manner, such as by click-through rate or other sorting rules to ensure that each query results The result positions are listed according to rules for easy positioning, and the font, font size, color are displayed for easy identification, etc.;
3. Title query, full-text search, fuzzy query, fault-tolerant query, multi-keyword organization query (spaces Are practical retrieval methods such as opening spaces) normal?
4. Are the style design and position of the control for inputting search conditions eye-catching for users to notice? Are there user-friendly designs such as snapshots and other shortcut viewing methods?
4. Compatibility
1. Application under various operating systems such as WINDOWS/LINUX/UNIX and under various versions
2. Application under various browsers such as IE/FIREFOX/GOOGLE/360/QQ, various versions, and various display resolutions
3. SQL/ORACLE/DB2/ Compatibility testing under various database storage conditions such as MYSQL
4. Compatibility testing under various language software platforms such as Simplified Chinese, Traditional Chinese, English and so on
5. Compatibility testing under various mobile application platforms such as IPHONE/IPAD and Android
6. Compatibility testing with various related monitoring programs, such as input method, anti-virus, monitoring, firewall, etc. Use tools simultaneously
5. Security
1. Deleted, encrypted, and authorized data are not allowed to be detected by attacks such as SQL injection. Is there any Security control design;
2. Enter some reserved characters for database queries, such as single quotation marks, %, etc., causing loopholes in the statements spliced out of the SQL query. For example, all data can be found, etc. In this regard, it is necessary to have some hacker attack ideas and introduce some tools and technologies, such as crawling.
3. Use white box testing technology to check whether there are any security risks in program design;
4. Contents involving national security and prohibited by law Whether relevant filtering and control have been carried out;
23,Account login:
1. Functional test
Normal
Enter the correct user name and password, click the submit button, and verify whether you can log in correctly.
Is it possible to jump to the correct page after successful login?
Function of remembering user name
Is the password non-clear text? To display, use symbols such as asterisks and dots instead.
When it comes to verification codes, you should also consider whether the text is too distorted to make it difficult to identify, consider the color (for color-blind users), and whether refreshing or changing a button is easy to use
Are the links on the login page such as registration, forgotten password, logout and login with another account correct?
When entering the password, there should be a prompt message when the uppercase keyboard is turned on.
Exception:
If you enter an incorrect username or password, the login verification will fail and a corresponding error message will be prompted.
After failed login, the password cannot be recorded
What should be done if the user name and password are too short or too long?
The user name and password contain special characters (such as spaces), and other non-English characters
Enter nothing, click the Submit button, and check the prompt information.
2. Interface test
1. Whether the layout is reasonable and whether the testbox and buttons are neat.
2. Whether the length and height of the testbox and button meet the requirements.
3. Whether the design style of the interface is consistent with the design style of the UI.
4. The text in the interface is concise and easy to understand, with no typos.
3. Performance test
1. Open the login page and check whether the required time is within the required time.
2. After entering the correct user name and password, check whether the time for successful login to jump to the new page is within the required time.
3. Simulate a large number of users logging in at the same time, and check whether the login jump can be normal under a certain pressure. 4. Under different networks (2G/3G/4G/5G), what is the response time of login and whether login is supported offline.
4. Security Test
1. Whether the cookie generated after successful login is httponly (otherwise it is easy to be stolen by scripts).
2. Whether the username and password are sent to the Web server in an encrypted manner.
3. Verification of username and password should be done on the server side, not just on the client side using javascript.
4. The input boxes for username and password should be shielded from SQL injection attacks.
5. The input box for username and password should prohibit the input of scripts (to prevent XSS attacks).
6. Prevent brute force cracking and detect whether there is a limit on the number of incorrect logins
7. Whether to support multiple users logging in on the same machine.
8. Can the same user log in on multiple machines?
5. Usability Testing
- Is it possible to operate entirely with the keyboard and is there any shortcut keys?
- Enter the username and password and press Enter to see if you can log in.
- Can the input box be switched with the Tab key? 4. Whether the password and user name can be pasted and copied.
6. Compatibility test
1. Can it display normally and function normally in different browsers (IE, 6, 7, 8, 9, Firefox, Chrome , Safari, etc.).
2. Can the same browser display and function normally under different versions?
2. Whether different platforms can work properly, such as Windows, Mac.
3. Whether it works normally on mobile devices, such as Iphone, Android.
4. Whether the display is normal under different resolutions. - Whether the page display is correct in different language environments 7. Scene interaction 1. Incoming call 2. Music is playing 3. Switching between front and back
24.If you were a quality inspector in a toy company, how would you ensure the quality of toys in terms of process control and use case design.
As a quality inspector for a toy company, my job responsibility is to ensure that there are no problems during the manufacturing process of the toys, and that the final delivered products are of high quality and safe. In terms of process control and use case design, I will take the following measures to ensure the quality of toys:
-
Process control: I will regularly check and evaluate the company's production and testing processes to check for any shortcomings and deficiencies that may affect product quality. If deficiencies are identified, I advise the company to adopt best practices to address the issues to ensure quality and continuity of the production process.
-
Use case design: I will develop a detailed set of use case designs for each toy to ensure that every step in the production process is checked and verified. These test cases will cover the entire process from providing raw materials to manufacturing, packaging and shipping. Use cases will cover key aspects such as size, weight, material composition, product appearance and more to ensure each product complies with specifications.
-
Sample testing: Samples are also selected from each batch during each production cycle for comprehensive testing and evaluation. These tests will cover various aspects such as product quality and safety, product structural integrity and comfort, and more. The data from the testing will help us identify any quality issues in the manufacturing process and be able to trace the cause of possible quality issues.
25, Test Tmall’s discount mechanism: the waiter will write the discount strategy into the database before the discount starts, and the system will read it into the cache; when the discount takes effect , you can consider testing points to ensure that the entire process is running correctly. (Two angles, waiter’s angle; user’s angle)
The following examples are for reference only, from the perspective of a waiter:
-
Verify whether the waiter writes the discount strategy correctly when writing to the database, and whether the discount strategy meets the requirements, including but not limited to discount rates, full discount rules, etc.
-
Verify whether the waiter's process of filling in the policy is normal, including but not limited to the UI for filling in the policy, the process of filling in the policy, etc.
-
Verify that after the preferential policy is written to the database, it can be read correctly and stored in the cache. If the cache fails, it can be reloaded correctly.
-
Verify whether the waiter can modify, delete and other operations before the policy takes effect, and whether the expired policy can be correctly sealed and terminated after modification.
-
When writing preferential policies, you need to consider concurrency, such as writing the same policy at the same time. You need to verify whether it can operate normally under concurrency and whether the number of writes is accurate.
Consider from the user's perspective:
-
Verify whether users can correctly obtain their current applicable discount strategies, and whether the amount of discounts and discounts has been correctly reflected when users purchase.
-
Verify that the user can cancel the offer before paying, and that the canceled status of the offer is correctly reflected and the payment amount needs to be recalculated.
-
Verify whether the user can be properly notified and provided with appropriate solutions if the discount policy expires or is modified during the purchase process.
-
Verify that users can get clear instructions and help when writing discount policies, and can understand whether the discounts they enjoy are compliant and reasonable, and whether there are other more favorable options.
-
When exceptions, errors and other abnormal situations occur, can they be adjusted and handled in a timely manner to avoid affecting the normal use of users?
26. Test cases for QQ login
27. Shopping cart test case
28. How to design elevator test cases
