Normalization And Readability

  1. It meets test plan specification requirements.

    • Collection of design/requirement documents for all features.
    • Test plan file and Screenshot are required.
    • You should invite reviewers.
    • It should have smoke test cases to ensure the product is ready for testing.

  2. The test plan must be structured and your overall thinking can be understood based on your test plan.


Completeness Of Coverage

  1. Focus on the business-related aspect of the product. These includes prototypes, functional tests and testing examples of scenarios.

    • Cover all new features and key expected results.

      • PRD（Pproduct Requirement Document）
      • DRD（Design Requirement Drawing）
      • DFV（Designs for Vision）

    • Consider influence between crossover modules.

    • Determine the test boundary to prevent the spread of tests.

  2. Nonfunctional requirements, including compatibility, security and performance stability.

    • Compatibility
      • Cross-browser, cross-device, cross-platform
      • Data Compatibility Test
    • Security
      • Performance Stability
      • APIs
      • Exception Testing
      • Event Tracking

Test Environment

  1. List reliable test environments and define test plans for the corresponding test environments.
  2. A targeted plan of relevant tests for the test environment.

Risk Assessment

Module Stability Risk

  1. Determine if it affects the stability of other modules.
  2. Determine if the relevant module person need to cooperate with the test.

Time Risk(Project Schedule Risk)

  1. Consider whether there are conflicts that affect the testing schedule.
  2. Consider if test time will take longer than expected.

Resource Assessment

  1. Combine with project progress to assess manpower and test time.