Test the theory - non-functional testing - performance testing and test analog peripheral

1 Overview

1. Before performance testing, it has been a little fuzzy
2. Now we encountered some relatively clear understanding of simple tidy

2. Performance Test

1. Performance Testing

1. Brief
   1. The most basic performance test
2. Scenes
   1. Test request
      1. attention
         1. Client
            1. Round-trip time
            2. Correctness

2. Load Test

1. Brief
   1. With a bias towards concurrent performance testing capabilities
      1. That the server can reach some kind of concurrency requirements
2. Scenes
   1. Using multiple machines on a single service, a lot transmits the request
      1. attention
         1. Client
            1. Response time
               1. average
               2. p90
            2. tps
         2. Changes in various resources
            1. cpu
            2. RAM
            3. Disk
            4. The internet

3. Pressure test

1. Brief
   1. With a bias towards concurrent performance testing capabilities
      1. Client: continuous pressure
      2. Server: Verify affordability
2. Scenes
   1. Using multiple clients on a single service, sending a large number of requests, the pressure increases
      1. attention
         1. Client
            1. Response time
               1. average
               2. p90
            2. tps
            3. other
               1. Each change of inflection point data
         2. Changes in various resources
            1. cpu
            2. RAM
            3. Disk
            4. The internet

4. Extension Test

1. Brief
   1. Try to add service in operation
      1. Expected response is the same, the capacity increase
2. Scenes
   1. While adding expansion, while adding user
      1. attention
         1. Client
            1. Response time
               1. average
               2. p90
            2. tps
            3. other
               1. Impact on the various parameters of expansion
               2. See if in line with expectations
         2. Changes in various resources
            1. cpu
            2. RAM
            3. Disk
            4. The internet

5. endurance test

1. Brief
   1. Long-running program
      1. Aimed at finding memory leaks
      2. It does not require continuous integration
2. Scenes
   1. Long-running, observe performance
      1. attention
         1. Client
            1. Response time
               1. average
               2. p90
            2. tps
         2. Changes in various resources
            1. cpu
            2. RAM
               1. Memory leak pay attention
            3. Disk
            4. The internet

ps

1. ref
   1. Continuous Delivery with Docker and Jenkins
2. Non-functional testing
   1. Outline
      1. Testing outside the functional test
      2. In addition to these performance-related tests, there are many other
   2. Other non-functional testing
      1. Safety test
         1. Concerned about security
      2. Maintainable test
         1. Concerned about code quality
      3. Recovery Test
         1. Focus on recovery after downtime
      4. other
         1. What feels like the compatibility test, but those points are not my concern
         2. Not list them