Another shout-out to @Nico Trummer, who finished PR #271 I started as a simple container optimization… which somehow (with all the versions updates) turned into a full test suite refactor 😅 Thanks a lot for all the time and effort you put into this. I believe it’ll pay off as a solid long-term improvement for the project!

Would the blogpost be on this by the way? Sounds like something worth writing one about to me

@Kurayi thanks for a gentle reminder 🙂 I am eager to finish my PR on adding a new tool to the pipeline, and then I don't mind writing a testing-related post!

Awesome! I'll be waiting to hear from you

The testing is a complicated topic, as certain unstabilities only arise on certain hardware, and I can only test on a limited set of different hardwares. I will be happy with it, once it works well on the hardware of all contributors (including you guys) But for now it's still not working well on Erik's hardware, so I don't think this is ready yet for writing a blog post about it But it also depends on what the content should be. If it is 'In #C077PUX8DBP we did this and it worked' then it's too early. If it should be about reproducibility of single-cell transcriptomics methods across different infrastructure and how this can be handled in an nf-core context, then we could do something already.

Blogpost topic is entirely up to @Kim Fehl, although a "We did this - it worked - this is how we made it work - maybe try the same on other pipelines" would be best

Just to get the contributions right here: In #271, Kim updated the module environments (which was of course good work, as it reduces the required disk space) - but everything related to the testing was done by me. Saying this because if such a blog post will be written by someone, it will mostly rely on my rationale Also if there should be any message of 'it works' in it, then it's too early for that

Most blogposts tend to be multi author anyway, and can be on pretty much any topic as long as you feel like writing it

No one is going to claim other's contributions or insights (though I have also been fixing some non-deterministic test output in another OSS project). We were merely discussing in my team some smaller issues (probably covered in the docs but still not so obvious) like calling

nf-test

with

profile=

vs

profile+=

. Though, I have not yet had a glance what the style of the blog is like and what readership it implies. If it is mostly for other seasoned contributors, probably such things won't be of interest for them. I was thinking more about guys like us, more or less describing our project onboarding experience and small things that can accelerate it for others. And testing part is usually less documented than the code itself, so I was thinking about targeting this gap, that's why I suggested testing topic in the first place, not because of the #271.

Simply describing your experience is welcome too tbh. Like I said blogposts can pretty much be anything as far as I have seen. You can opt to wait for the tests aspect to be complete first then if you'd like to write something more technical