we have some composite tests that use a common dictionary encoded in another composite test. We used the “composite” type instead of “composite string” when we developed this in 0.3.0.
Now we’re in 0.3.1, and there’s the new “composite string/json” type, but we haven’t changed our code. And submitting test is fine.
however, we’ve tried to lately to submit a test as “in progress” and now the app raises an error about our dictionary composite test, that says “please enter a number”. So I figured the composte is supposed to return a numerical value.
I thus saved another composite/json test with our dictionary and put this one in the test list instead of the composite one. Now it’s fine.
This all makes sense, except for the fact that we never saw any error or exception raised before, while from the start, we shouldn’t have used a composite test for returning a dictionary.
It might be good to solve this at the higher level, while creating the test itself. There could be a check that the type of the returned variable is numeric. If not, raise an error. This would be particularly helpful since we cannot now change our original composite test to composite/json because tests have already been performed with it.
Another possibility is to check while performing the test list and submitting it, not only for an “in progress” submission but any submission.