1. Basic elements of product testing

(1) The appearance of the product interface test: test whether the appearance of the product interface is beautiful, whether it conforms to the design specifications.

(2) Functional test of the product: test whether the functions of the product are in normal use.

(3) Product performance test: test whether the product can maintain its stability in a specific environment.

(4) Product security test: test whether the product itself or in the process of use will produce security problems.

(5) Product usability test: test whether the product is complex to use and whether the user experience is good.

(6) Product compatibility test: Test whether the product can be compatible with other products during use.

2. What is software?

All applications installed on a computer’s operating system can be called software.

3. How to review requirements documents?

(1) Correctness: Check whether the requirements document formulated by product personnel deviates from the original requirements of users according to the original requirements of users.

(2) clarity: check whether there are some ambiguous words in each requirement item in the requirements document, whether the terms are clear and whether there is ambiguity.

(3) Completeness: according to the original requirements of users, check whether the requirements document formulated by product personnel covers all requirements put forward by users, and whether each requirement item omits some necessary information put forward by users.

(4) Restriction: each requirement item clearly describes what the software can do and cannot do, what it can input, what it cannot input, what it can output, and what it cannot output.

(5) Priority: which functions are more important and which are less important in the requirements document, and whether they are marked and numbered.

(6) Consistency: Check whether the content in the requirements document is consistent to ensure that there is no conflict or contradiction.

4. Review focus?

  • The test method adopted
  • Path composition for process tests
  • The basis on which equivalence classes are divided
  • Data comparison of selected objects and data checkpoints
  • Test data selection and preparation methods
  • Whether to simulate data and the method of simulating data
  • Risk-based test trade-offs

5. Purpose of review

  • Render the test work
  • Agree with development
  • Different ways of thinking collide and spark, borrowing from others’ ways of thinking.
  • Develop the behavior pattern of being willing to contribute ideas to your team or others
  • Give full play to teamwork, maximize personal experience and expertise, and achieve complementary skills.