Alternate Request without 'method' query parameter is issued by conformance test

[dkudinov]

I'm trying to run xAPI Test Suite for LRS and error I'm getting is this:

"During LRS configuration validation:
Error: Expected response status code to be 200 got 500"

From detailed logs of requests I see, that request is sent with POST method to /xapi/statements without any parameters in query string while according to specification (https://github.com/adlnet/xAPI-Spec/blob/master/xAPI-Communication.md#alt-request-syntax) it should include 'method' parameter in query string.
Example LRS _ Separate LRS.txt

[cr8onski]

Is this the only test you are failing?

From the looks of it, this is from the pre-test/setup portion of the test, and will be sending a regular request syntax to the lrs. The alternate request syntax tests won't be tested until later in the suite.

[dkudinov]

Test suite is failing after that request with 0% completed and results "0 passed 1 failed".
Still, I would like to understand if issue is in LRS under test or in Test Suite. According to logs I got (see attachment in my original post), request sent to LRS is invalid/doesn't comply to specification. However, I'm not sure if I interpret logs correctly and could it be that LRS behavior is incorrect.

[cr8onski]

That first test runs before all the others and established two things. One that you can reach the LRS. Two it establishes a time difference between the system the LRS is on and the system the Test Suite is on. To do this, this test sends two normal requests to the statement resource, a normal post and a normal get.

The Alternate Request Syntax is to handle a special case for LRS's to accommodate those using older browsers (like IE 8 or 9) to be able to send statements despite the cross origin request restrictions of those older browsers. These tests will all run as part of the test suite after this initial test passes.

If you'd like to run just those tests specifically, you can use node bin/console_runner -e <endpoint> -a -u <username> -p <password> -g "Communication 1.3" on the command line or check the Alternate Request Syntax Requirements box in the requirements area under the Advanced Test option if using the UI.