Issues with logical AND/OR tests

[thefotios]

I know these were old issues (#296, #305) that were explained, but this came up again for me.
The explanations totally make sense, but the tests still do not seem to support them.

I modified what I believe are the test security definitions to match

# OR
security:
  - handler1: []
  - handler2: []

# AND
security:
  - handler1: []
    handler2: []

// OR
"security": 
  { "handler1": [] },
  { "handler2": [] }
]

// AND
"security": [
  {
    "handler1": [],
    "handler2":[]
  }
]

i'd like to bring this up here with an example just to make sure I'm not crazy before I embark on trying to fix this.

I also noticed that this block might be better written as:

async.some(securityReqs, function (secReq, cb) { // logical OR - any one can allow
  ...          
  async.every(Object.keys(secReq), function (name, cb) { // logical AND - all must allow

but this would require changing the callbacks and whatnot to not have to short circuit them.

Questions

1. Am I completely missing something with those tests that I changed? Not sure if the helpers are doing something that I missed.
2. If this is a bug, should it be fixed? If so, it has been live for a long time and may have serious repercussions.

[whitlockjc]

Do you mind looking into this @theganyo?