Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LTS: specify limit when loading statements #17

Open
cars10 opened this issue Oct 21, 2021 · 2 comments
Open

LTS: specify limit when loading statements #17

cars10 opened this issue Oct 21, 2021 · 2 comments

Comments

@cars10
Copy link

cars10 commented Oct 21, 2021

Hi,

we use a fairly low default limit of 5 statements per query if you do not specify a limit. This leads to issues with some tests in the LTS, the first one being https://github.com/adlnet/CATAPULT/blob/main/lts/__tests__/runtime.js#L95 because it expects a result with at least 6 statements on one page.

If a test expects more then one statement we should explicitly specify a limit to prevent this.

Edit: i think you are theoretically allowed to limit every request to just 1 result, regardless of what limit is provided by the client. So the better solution might be to follow the more property when we expect more then one statement?

@gavbaa
Copy link
Contributor

gavbaa commented Oct 25, 2021

Per the xAPI spec: https://github.com/adlnet/xAPI-Spec/blob/master/xAPI-Communication.md#partthree

The LRS can choose any size limit it sees fit, but needs to be configurable so as not to apply size limits during conformance testing. Of course, some size limits will still exist during conformance testing due to limitations of hardware, etc. but it is expected that these limits are sufficiently high so as not to affect the running of tests.

My reading of this is that it's completely on the LRS provider to make sure that they use limits sufficient for conformance testing, not for the test suite. In this case, it might be valuable for us to document what the LRS should be set to for a minimum limit as part of the LTS docs, but I don't believe we should do anything additional on the tests themselves.

@cars10
Copy link
Author

cars10 commented Oct 26, 2021

but needs to be configurable so as not to apply size limits during conformance testing

This is a very valid point :) I agree that it simply comes down to missing documentation then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants