Plans to support "integerValue" and "booleanValue" in test specification

[Brian Correa]

Hi,

I'm curious whether there are any plans to support integer and boolean values as a payload datatype. I am currently working around this limitation by casting "stringValues" to integers. Initially I wanted to use longs, but am seeing this Exception when I attempt to load my test matrix. I've included a sample schema and test definition below. 

Schema

"payload" :{

   "type": "map",

   "schema": {

       "modelId" : "stringValue",

       "runExperiment": "stringValue"

    }

}

Test Definition

"payload": {
    "map" : {
        "modelId": "1",
        "runExperiment": "1"
     }
}

Thanks,

Brian

[Tibo Kruse]

Hello Brian,

if you cannot use "longValue" in your schema, that would be a bug. Can you post the actual exception message, and the Schema and test definition you tried with Long.

So far, internally it has not been discussed whether adding boolean and integer on top of the currently supported types would be valuable enough to implement.

In your testDefinition, you seem to want to set a boolean flag "runExperiment", yet the typical way of enabling/disabling experiments would be to change the allocations or allocation rules. Is there a reason you did not want to do that?

regards,

  Thibault

[Jack Humphrey]

Please also check which version of Proctor you are using, and specify that along with the other info that Tibo mentions.

I've updated the proctor-demo example to use a map payload with a stringValue and a longValue, and it's working fine (live site).

Here's the specification, and here's an example definition.

Hope that helps.

Jack