You're viewing a single thread.
See your problem is you're editing the code until it passes the tests. It's way easier if you edit the tests until it passes the code.
217 1 ReplyThis is what they mean by test driven development.
108 0 Replycastle.gif
5 0 Reply
Can't tell if you are joking. I know a lot of junior developers who think this is a legitimate solution.
36 1 ReplyUnless you are using groovy (jenkins), then you are running the pipeline to find syntax errors.
23 0 ReplyThis comment is triggering and it should have a NSFW spoiler.
15 0 ReplyI hate groovy, gradle and Jenkins!
I don't know if sth. Else is better but I can confirm that shit is horrific
6 1 ReplyWhy do you hate groovy?
2 1 ReplyHorrible scripting language. Even worse than python. Close to Javascript
2 2 ReplyIf you don't think Python is a good scripting language, what is a good scripting language in your opinion? Bourne Shell? VBScript? PHP?
4 0 ReplyI like python and if you use typing it is awesome.
I like kotlin script too. But normal languages are better than scripting languages usually.
2 0 ReplyTyping in python leaves a lot to be desired... Being looking at peps for quite some time, but it's really hard for the language to make progress without breaking compatibility.
Hopefully at some point MOJO becomes mature enough to use in a professional setting.
2 0 Reply
FYI, Jenkins has an endpoint to validate the pipeline without running it, and there's a VSCode extension to do this without leaving the editor: https://www.jenkins.io/blog/2018/11/07/Validate-Jenkinsfile/
4 0 ReplyI am not using Jenkins anymore but this seems like a lifesaver, thanks for sharing
2 0 ReplyI use Jenkins for work, unfortunately, so I have plenty of experience
1 0 Reply
Only for declarative pipelines, forget it if you use scripted ones.
1 0 Reply
I just replace all my tests with noop codes. Quick, easy, passes.
7 0 ReplyIf true == true pass!
4 0 Reply