HI , 1) There are some sample input data for tools in CWL Git repository .If not i will create own input data for testing .
2) There are real cwl tools in Git repository can't i use them or you are referring to another approach ? 3) Yes i need to check that .But i thought i will engage with CWL community when creating YAML parser is that okay ? 4) Don't i need to change proposal and put these details in.Also about Time management ,can you tell me whether i did write or wrong On Tue, Mar 22, 2016 at 5:27 PM, alaninmcr <[email protected]> wrote: > On 22/03/2016 11:46, Thilina Manamgoda wrote: > >> a)Please can you be more specific ? >> > > Where will you get your CWL tool descriptions from? I think this is where > engagement with CWL community will help. > > You need two kinds of test data: > 1) Data written to test specific functionality of your tool. So unit tests > with associated input data and expected output data. Those tool > descriptions do not need to "make sense" as real functional tools. > > 2) Real tool descriptions corresponding to real tools that would run in > CWL. You need to test that your plugin works with these real examples. > > b) No i will use examples in CWL git repositories >> > > I think you need to check that the examples in CWL git repositories cover > all the possibilities. > > c) At the moment Tutorials for plugin creation are fo Taverna 2.So i have >> to test it on Taverna 2 and then convert it to Taverna 3 >> > > You need to have a plan to test it. That does not need to be in the > proposal, but you need to have a stage for deciding how you will test the > plugin. > > Alan >
