...

• Dynamically clones process flow subgraph region
• Used for repeating steps for independent portions of test environment
  • e.g. install, uninstall, collect logs on all ONOS instances concurrently
• Has an iteration variable specified as ${var#} property
• Clones subgraphs for each of var1, var2, … varN
• Stops cloning when varX becomes undefined or empty
• Value N can be abstracted using ${#} special property
• The <parallel> tag itself does not support the name or requires attributes. However, you can wrap the parallel chain in a group tag to get the same effect.

Sequential Chains

• Dynamically clones process flow subgraph region
• Used for sequencing steps for portions of test environment
  • e.g. process a task for all ONOS instances sequentially
• Has an iteration variable specified as ${var#} property
• Clones subgraphs for each of var1, var2, … varN
• Stops cloning when varX becomes undefined or empty
• Value N can be abstracted using ${#} special property
• Value N-1 can be abstracted using ${#-1} property

...

• Inherent dependencies specified as requires attribute of each step and group element
  
  • specified as comma-separated list of step or group names
• Injected dependencies specified as requires attribute of a dependency element
  
  • used for chaining steps or groups imported from other scenarios
• Hard dependencies
  
  • forces wait and failure of predecessor results in step being skipped
• Soft dependencies - designated by “-” prefix
  
  • forces wait but failure in predecessor has no impact
• The "^" requirement is used to indicate the previous step. Note that this only works between a step and a step. If one of the linked steps is within a different group, parallel, or sequential chain then you must specify the requirement by name.