Chloe Thurman asked, "In what language are the tools primarily written?"
Here are the tools that I showed in my presentation, directly or indirectly. As I mentioned, there are many tools for any given task, and these are merely the tools that most of us are using today within the JMP Live team.
Tool: Jira
Shown in: "Find a Need", "Commit Code"
Written in: Java
Website: https://www.atlassian.com/software/jira
Tool: WebStorm
Shown in: "Understand the Need", "Write Code"
Written in: Java
Website: https://www.jetbrains.com/webstorm/
Tool: Confluence
Shown in: "Design"
Written in: Java
Website: https://www.atlassian.com/software/confluence
Tool: ESLint
Shown in: "Static Analysis", "Continuous Build"
Written in: JavaScript
Website: https://eslint.org/
Tool: Jest
Shown in: "Automated Tests", "Continuous Build", "Test by Professionals"
Written in: JavaScript
Website: https://jestjs.io/
Tool: DBeaver
Shown in: "Manual Tests"
Written in: Java
Website: https://dbeaver.io/
Tool: Swarm
Shown in: "Peer Review", "Commit Code"
Written in: PHP, JavaScript
Website: https://www.perforce.com/products/helix-swarm
Tool: Perforce
Shown in: "Commit Code"
Written in: Unknown to me, was not trivial to find the answer online
Website: https://www.perforce.com/products/helix-core
Tool: Bamboo
Shown in: "Continuous Build"
Written in: Java
Website: https://www.atlassian.com/software/bamboo
Tool: SauceLabs
Shown in: "Test by Professionals"
Written in: Unknown to me, was not trivial to find the answer online
Website: https://saucelabs.com/
@elaine_daniloff said "I struggled with accessing JMP Live..."
I'm assuming that this was not a small typo (of the type I often make) and you were not asking about accessing JMP On Air (our online content hosted by Julian).
I'm assuming that this question is really about accessing JMP Live (our JMP collaboration software).
Check out this overview of JMP Live: https://www.jmp.com/en_us/software/collaborative-analytics-software.html
Check out JMP Public, a publicly available version of JMP Live: https://public.jmp.com/featured
Bill Ross asked "How often do you design experiments to test your code for different customer environments (Conflicting OS, other software, etc.) so over changing noise?"
@bradleyjones mentioned that JMP has a great DoE feature for Covering Arrays (https://www.jmp.com/support/help/en/15.2/index.shtml#page/jmp/covering-arrays.shtml#).
@Audrey_Shull (Sr. Manager, JMP Development Testing) answered this in more depth after JMP On Air concluded: "Quite a few people have used covering arrays for desktop JMP features, when the input space can be somewhat easily defined. For example, I remember writing tests for Graph Builder, and there are so many roles and elements - we created a covering array and defined a factor for each role, and the levels were Continuous/Ordinal/Nominal/Missing/None for each role. The test group also uses covering arrays routinely for installer test planning at the end of each release to make sure we have enough test combinations for operating system, JMP upgrade path, JMP vs JMP Pro vs JMP Subscription, language, etc. To my knowledge we haven't been using them for JMP Live - and most of the functionality is not defined by those kinds of dimensions. There might be some things we could incorporate though, in particular I'm thinking of the Admin pages where there are so many options."