General Check List before upgrade to new version

Question

Hello,

Recently we had one customer complained about their customized JSL not working after upgrade from JMP13 to JMP15.

Learned from this case, seeking advice on a more general situation:

Do we have a kind of general check/testing list guide for customers to test on 1-2 computers before all the users migrate to the new version?  thank you

DonMcCormack · Accepted Answer

@PIN ,

We (me, Mark Bailey, Mark Anderson, & Ian Cox) are working on a short guidance document to outline good programming practices. While it will be general and not contain a detailed set of instructions as to how a script should be tested, it may form the foundation of future guidance documents. We hope to have something by midyear. Ultimately, as you mention, it's about testing, which should be conducted when the beta release of a new version becomes available. In the case of a script not working, it helps understand what is happening (i.e., what error conditions are occurring) and why.

MikeD_Anderson · Accepted Answer

@PIN, just to tack on some thoughts to Don's points.  The JMP Scripting Guide (part of the documentation) has an appendix on potential compatibility issues between versions.  This appendix is in each version of the Scripting Guide (all online), so a user can work through those changes and see what might be a problem.  There is also a section in the New Features document included in the install (under help) that discusses changes to JSL in the current version.

I also add a +1 to Don's comment about checking JSL in the beta phase.  Since things are fresh in the developers' minds and they know what's changing between each EA release guidance can be offered through the beta mailing list on what might have broken.

Another thought - point out that they can use the JSL Debugger to pinpoint where in the code the problem is coming from.

best,

M

PIN · Accepted Answer

Thank you so much @MikeD_Anderson @DonMcCormack

Regarding this, even though we don’t have an official checklist for the user before upgrade to new version JMP (not limited to JSL).

However, pen down few points which I think could be useful:

1st to check are those “Commonly and Heavily used JSLs”, please do a throughout run check to make sure everything works well

2nd to check are those reporting templates, to make sure the graphs are same or better presenting (a bad example is the variability chart case before ☹)

The last thing to take note is the windows system compatibility, usually, there will be no problem, but just in case some users using different or older version windows may have a different result as what you have (This case happens before: window7 vs JMP15 ☹)

Thanks again for sharing :smiling_face_with_smiling_eyes:  and wish all of you a good weekend :smiling_face_with_smiling_eyes: