You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In python unit test, functions can be mocked so they returns certain values or data without going through the processes that takes long time, and only for the purpose of testing. So I'm thinking that would be great if we can somehow implement the mocking in nftest. A naive thought is that we can analyze the process/workflow definition and figure out the input output file pattern, and replace the code block with user specified code, or use existing files to mock the output files of the process. This will let it test the process/workflow logic without waiting for hours for the actual tool to run. @uclahs-cds/nextflow-wg @uclahs-cds/software-wg
The text was updated successfully, but these errors were encountered:
I agree this would be useful; I don't know if we'll be able to completely implement mocking but I do have some ideas on adding some way to test a specific process rather than having to run the entire pipeline. Will keep you posted!
In python unit test, functions can be mocked so they returns certain values or data without going through the processes that takes long time, and only for the purpose of testing. So I'm thinking that would be great if we can somehow implement the mocking in nftest. A naive thought is that we can analyze the process/workflow definition and figure out the input output file pattern, and replace the code block with user specified code, or use existing files to mock the output files of the process. This will let it test the process/workflow logic without waiting for hours for the actual tool to run. @uclahs-cds/nextflow-wg @uclahs-cds/software-wg
The text was updated successfully, but these errors were encountered: