I. Project Description

  1. Integrate design draft and PRD demonstration program functions to ensure the integrity of requirements.
  2. Verify that new dependencies, such as components and Node modules, have been introduced during development.
  3. Confirm the code variation range of this requirement and prepare ChangeList in advance for efficient review.
  4. Check whether the requirements involve the front-end and back-end services.
  5. Verify that documentation is documented for this request.

Second, key business

  1. Make sure there is any real money involved, such as reservation, coupon, purchase, settlement, etc.
  2. Verify that the service side CRUD logic is involved, as errors can be passed through.
  3. Confirm reconfirm the core business code for this requirement.

Third, coding design

  1. Identify code design hierarchies and data flows.
  2. Verify component separation and design, such as single responsibility, coupling, etc.
  3. Verify that methods in a module or component can be moved to a separate file module for maintenance to make the module or component more concise and readable.
  4. Verify that the project has README file content.

4. Coding specifications

  1. Confirm the naming conventions.
  2. Make sure your comments are clear and useful, and use them only to explain why not what, and make necessary comments for convoluted logic.
  3. Verify that hard-coded data is correct, such as link addresses.
  4. Check whether the timer is reasonable and do not abuse the timer.
  5. Verify that variables have made the necessary null and type judgments.
  6. Verify that the deep logical nesting is properly designed and reasonable.
  7. Verify that recursion is used directly or indirectly to ensure that recursion can be exited.
  8. Verify that the conditional expression is not too complex and make sure that the conditional expression is unambiguous.
  9. Verify that global variables are used for communication and disallow this behavior.
  10. Check whether the array is modified while iterating through the array, which will cause the array length to change and cause a program error.
  11. Determine if the body of the function is too large to read and maintain.
  12. Confirm the monitoring scenario.

5. Environment configuration

  1. Verify that the domain name and data configuration related to the test and formal environment are correct.
  2. Verify any changes to CICD (Continuous integration and deployment) configuration.
  3. Verify whether the configuration of the front-end engineering build has changed (Webpack, ESLint, Babel, package.json, etc.).

Vi. Compliance issues

  1. App& Small program Anti-violation Operation Guide 1.0.
  2. Confirm whether there is relevant information publicity for the lottery activities.

7. Technological precipitation

  1. Verify that there are outputs for common components, methods, and common business processing scenarios.

To be continued…