[TASK] Test if #35 (statistics retrieval for an individual fire point vertex) is working.

[spydmobile]

ref: #35 @RobBryce confirmed this is done, it just needs testing so assigning to @nealmcloughlin

[spydmobile]

@nealmcloughlin checking in if you can test this one

[spydmobile]

hi @nealmcloughlin please test this, thanks!

[spydmobile]

@RobBryce nobody can test this but you, please add it to you pile. Nobody has a clue what the error codes are or what they mean.

[BadgerOnABike]

Would you mind providing the method with which you generate these error codes as well. This will serve the purpose of learning how you are doing this testing as well as expanding our automatic testing into the future.

[RobBryce]

The code has been fixed. The situation where error codes could be generated shouldn't exist unless there is a programming error - which is intended to help find bugs moving ahead. This is far internal to any code that would see any form of automated testing.

[BadgerOnABike]

If this is to be tested in WISE, are we able to do it with the current JS API or does that need to be updated first?

@spydmobile

[spydmobile]

@BadgerOnABike I dont know. I am guess, there has been no change in the JS api for a while and we likely need to wait for a successful new build to find out. Am I out to lunch here @RobBryce ?

[RobBryce]

This code is so buried from any JS API call that (discussed before), there's no easy way for you to test other than to confirm that grid exports for simulation statistics look correct. The error condition shouldn't have occurred anyway, but this was done in the interests of keep the code clean, and to catch future bugs from future changes in the code.

[spydmobile]

thank but @RobBryce the question is, "Can we test this with the current JS API" or not?

[RobBryce]

Not directly.