Shulou(Shulou.com)06/03 Report--

After a period of time, many people have their own plans. Some people are ready to engage in other aspects. Some people are ready to continue to strengthen themselves and become an elite test engineer. This article will provide you with another option. From test engineer to product manager, for you who are now a test engineer, if you have plans in this regard, you can start preparing according to the information in the article. In the near future, You are a good product manager.

Product Manager, a multi-skilled position, may be required to perform both product and test functions in understaffed companies. When we have finished product manager documentation, review, follow-up development work, and finally get the version submitted by the developer, how should we find as many bugs and non-conformities as possible in the test? Here are 10 ways to get better at testing.

1. UI Design Test:

All the fields, pictures, icons and other interface elements contained in the page shall be accepted and fed back by the product manager together with the designer according to the design requirements.

2. Test Case Testing:

Write test columns according to prd (you can follow normal flow/abnormal flow/branch flow, and use causal diagram to traverse functions), test cases need to traverse all functions, test according to test cases, but also more convenient for bug positioning.

3. False Assumption:

Inferring bugs that might occur based on experience and intuition and designing test cases for them as a way to supplement test cases.

4. Character test:

Input test according to special characters, length, emoji, Chinese and English, symbols, threshold limits, etc.

The above 4 items are not difficult for general test engineers, but they are things that can be easily done in 1-2 years, so the following 6 items are the ones that need everyone's attention.

5. Cache Test:

From the cache data and size (peak setting), cache time, cache environment (with or without network), cache storage methods and other aspects.

6. Most/Few Tests:

Threshold, observe the reaction and display of the system (generally refers to pressure test, need to use some platform to operate).

7. Multi-environment/external environment test:

Different versions of the same system, different screen resolutions, different manufacturers of equipment, GPS (off or poor), camera, loading time and other conditions of the test.

8. Accuracy test:

Relevance and accuracy of search data results.

9. Sort test:

According to the product design rules, sequencing test and adjustment. (including message list, product list, time, etc.)

10. Account Test:

Account login for the first time, new account login, multiple logins of different models of the same account, data display test when different accounts of the same device login.

Is the above 6 items also common to everyone, but this is the product manager's focus on the problem oh

These six methods are cross-used with test cases to ensure that most users can be traversed for what happens. However, no one is perfect, the program will be more or less wrong, I hope through a little experience sharing, let more product people in the design of products and testing logic more rigorous, their products polished better.

Well, you've read my article, and I'll keep my word and share it with you.

Interface test related data

Link: pan.baidu.com/s/1ojpoWnpxxReR1sO2Gxy_YQ Password: dgfa

Performance test related data

Link: pan.baidu.com/s/1_oZhvOIRvcz0JGcCWUGT-g Password: d82b

Software Testing Getting Started Upgrading eBooks

Link: pan.baidu.com/s/1Fp8CFE0D2p0uAZk6xcexhQ Password: exna

Automated testing related materials

Link: pan.baidu.com/s/1yeD1EMg-HalNuRBDODGx7g Password: ofdg

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.