Skip to content

Test scenarios #58

@hagai-lvi

Description

@hagai-lvi

list of (manual) tests we want to perform before submission

Ordered from the most basic one to the most complicated
After each test, make sure that all the resources were cleaned up

  • 1 local, 1 task
  • 1 local, many tweets
  • 1 local with small task, then 1 local with big task
  • 1 local with big task, then 1 local with small task
  • many (many) locals simultaneously
  • many locals with small tasks, then many local with big tasks
  • many locals with big tasks, then many locals with small tasks
  • multiple locals, with growing number of workers for each local (i.e: local-1: 1 worker, local-2: 2 workers, etc) - make sure that the workers are actually added
  • killing a worker for a task with single worker
  • killing a worker for a task with multiple workers
  • killing a manager (I believe that there is a problem with this scenario because 2 different managers will create the same queue for the same task, we need to think of a way to overcome this)
  • killing a worker(s) and the manger
  • 5 locals with terminate=false, then 1 local with terminate=true, then 5 locals with terminate=false, then 1 local with terminate=true.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions