308976_en-US

liliconcom

Script validation for each release change

Hello, 

 

I have a client who has a large number of scripts (> 2000) and whose release change has a real cost. 

Indeed, he must validate all his scripts on the new release before deploying it. 

 

Would there be people who would have experience on it and who would have for example a JSL script capable of testing and validating a set of scripts? 

 

or another approach that would be effective?

Thank you for your suggestions.

Best regards, 

 

Florence 

Re: Validation de script pour chaque changement de release

Hi @flo_kussener,

this would be another great topic for the JMP Scripting Unsession at Discovery Summit Americas on October 12.

I think there would be many customers interested in the topic.

Please consider hosting such a session or dropping in to share some of your concerns.

 

cheers,

Stan

Re: Validation de script pour chaque changement de release

Hi Florence,

 

in general there are two things one should follow when doing extensive coding or programming:

1. Following good programming standard/guidline

2. unit testing

 

A good programming standard can help to prevent many different coding styles and some quite common mistakes or potential issues. It might differ from company to company in the details but the general guideline for good programming remains.

 

Unit testing helps to see if the code will provide the expected results. This can be done for code snippets or complete scripts. usually you will get a test log where all successes and errors will be listed. This helps to fasten up validation as you can always point to that unit test script and share the results with authorities. For 2000 scripts this might be a lot of initial work but from there ongoing usually only minor changes are necessary, e.g. when adding new tests.

 

JSL-Unit-Automated-JSL-Testing is a basic version of a unit test for jsl scripts to get you started. 

Also this thread might help: https://community.jmp.com/t5/Discussions/Regression-testing-JSL-scripts-on-new-releases-of-JMP/td-p/9109 

 

My honest opinion: I'd wish that we take more care of jsl backwards capability testing as almost every release there will be a change in arguments, in/outputs, or complete jsl functions behaviour (e.g. sorting) which either breaks scripts or provide different outputs. I know we provide scripts and no programming language, however ... 

Re: Validation de script pour chaque changement de release

Just to add, this US 2020 Discovery Summit Presentation next week should be handling exactly this topic so you might want to tell your customer:

Creating a JSL Script Ecosystem: GIT, Unit Test, VBA for PPT, Crash Log Collection and More