The any type allows us to assign literally “any” particular value to that variable, simulating what we know as plain JavaScript – where types can dynamically be assigned from different types, such as a String value becoming a Number.
The any type should really be used when we don’t actually know what type is actually coming back to us. This could be, for example, through a function argument that’s part of a third-party library and it doesn’t have any type definitions.
Because the type that is used is not clear beforehand, the AppTester cannot know how to send data to BAW or assert data without telling the AppTester what we should expect. So for the ANY type in the AppTester, the AppTester Expects jSon in which you define the type of variable the any type is at that moment.
In the next table we have examples on how to do that: This table is also available as an Excel download here.
| Any Type | IBM BAW | AppTester input | AppTester Assert | Note |
| Default Template |
{ “@type”: “String”, } |
{} | ANY type is anonymous type, correct data type is determined in run time so user need to input a data type specifically | |
| Simple Type (String, Integer, Boolean,…) |
//String //Integer //Boolean |
// String “@type”: “String”, } // Integer “@type”: “Integer”, } // Boolean “@type”: “Boolean”, } |
// String // Integer // Boolean |
– @type is correct data simple type. For example: String, Integer, Decimal, Boolean. – value is data value |
| Complex Object |
tw.local.profileType = {}; tw.local.anyType = tw.local.profileType; |
{ “@type”: “JobType”, { “id”: “1”, } } |
{ “id”: “1”, “title”: “Developer” } |
|
| ANY Array |
[ { ] |
|||
| Any – Map |
{ “@type”: “Map”, { “key”: 1, } } |