Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extend support for nf-test 🚀 #63

Open
sateeshperi opened this issue Nov 11, 2024 · 3 comments
Open

Extend support for nf-test 🚀 #63

sateeshperi opened this issue Nov 11, 2024 · 3 comments

Comments

@sateeshperi
Copy link

There are several ways that the language server might be useful for checking .nf.test files, which is now the testing standard for nf-core and several nextflow pipelines.

Some common things that the server can check for are:

  • missing , in multiple assertions in then block
  • inputs are not numbered like input[0]
    (will add more)

Would like to know if this is something that the server can check for ?

@maxulysse
Copy link

@lukfor any extra ideas?

@bentsherman
Copy link
Member

The nf-test scripts would require a custom parser for their syntax, or to re-use the Groovy parser with some custom AST visitors to validate the raw Groovy code

I am considering this, but I am also considering adding a native testing syntax into the Nextflow language based on nf-test. That would also be the proper way to deliver some of the highly requested features for nf-test like better inputs and cloud execution.

So I'm not sure if it's worth all the effort to support nf-test as it currently exists

@sateeshperi
Copy link
Author

cc @lukfor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants