XAPI-00171 doesn't accept substatement activity object with objectType

[István Rátkai]

'should process using GET with "format" ids (XAPI-00171)'

in line 1297 of H.Communication2.1-StatementResource.js it checks the keys in the subStatement's object:

expect(Object.keys(stmt.object.object).length).to.eql(1);

But that is an activity, so the objectType key optional. The proper check should be:

expect(Object.keys(stmt.object.object).length).to.be.within(1, 2);

[Thomas Turrell-Croft]

@milt I would appreciate your thoughts on this issue.

[Trey Hayden]

Had to look over this for a second, but everything seems correct.

In this case, it's requesting a specific statement back that it'd sent earlier in the test prep. The sub-statement in question that it's checking against is: https://github.com/adlnet/lrs-conformance-test-suite/blob/LRS-2.0/test/v1_0_3/templates/statements/unicode.json

Since that particular request is using format=ids and providing a specific statementId to get the specific one it sent earlier, the LRS is expected to reply with only that one statement and to exclude all non-essential information anyway, so the expected sub-statement would still be fine -- as its objectType value of Activity is the assumed one anyway, and can be excluded.

It does seem a tad opinionated though.

[Thomas Turrell-Croft]

@Selindek I think that this issue can be closed because I believe that this test in the test suite is correct according to the xAPI specification.

It might be said that the xAPI spec should make ObjectType mandatory to avoid edge cases like these but that is a different issue.

@vbhayden thank you for looking at this, I really appreciate the time you have spent on it. The test suite is a valuable resource for vendors.