Right now the test notebooks are created by splitting the json at intervals of 100 tests.
This creates notebooks that are larger than is ideal and also loses the opportunity to group together important information about the types of tests contained in the notebooks.
Inside the json spec, it should be possible to distinguish which features are being tested by which tests. We should create notebooks on the basis of those distinctions.
So, for example, you would want to group all of the tests related to lists in a single notebook.
If one feature ever has more than 100 tests, then it may make sense to split it into multiple notebooks (ideally, on the basis of some systematic feature of the tests). However, I do not think that is the case today and so we shouldn't need to worry about that.
Right now the test notebooks are created by splitting the json at intervals of 100 tests.
This creates notebooks that are larger than is ideal and also loses the opportunity to group together important information about the types of tests contained in the notebooks.
Inside the json spec, it should be possible to distinguish which features are being tested by which tests. We should create notebooks on the basis of those distinctions.
So, for example, you would want to group all of the tests related to lists in a single notebook.
If one feature ever has more than 100 tests, then it may make sense to split it into multiple notebooks (ideally, on the basis of some systematic feature of the tests). However, I do not think that is the case today and so we shouldn't need to worry about that.