Ask HN: How do you build and test your Jenkins pipelines / libraries?

There seems to be a problem with scripted pipelines and Jenkins: due to the fact that Groovy is mostly used and the fact that Jenkins injects a lot of runtime variables (including plugins), it is really difficult to set-up an IDE and a testing environment for Jenkins pipelines / Shared Libraries... without spinning up a Jenkins instance. What are your thoughts on the topic? What are some of your suggestions?