Ideas for stress testing

• heavy load:
  • large number of users
  • large volumes of data
  • large number of processes
  • large number of transactions
• constrained resources
  • not enough memory, processing power, or disk space
  • not enough bandwidth
  • not enough queues (or even shallow queue depth)
  • not enough licenses
  • inability to access files, servers, or services
• unfriendly inputs
  • invalid file types and/or data types
  • fuzz testing
  • very large (or very small) inputs
• shared resources
  • crash or stress other applications in a shared server space or that use a shared device/service
• timing
  • constant or steady load for long periods of time (endurance)
  • intermittent loads with long pauses in between transactions (looking for timeouts or parts of the system that go to sleep or get deprioritized with inactivity)
  • concurrency (trying to force potential race conditions, file/database locking, etc...)