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
The cli-rs do not count with unit testing, so it is required to write tests that can be run with the cargo test command and that test behaviors at the command line. These should be exhaustive, meaning they should test for all the commands and options combinations and provide an acceptable coverage level, i.e., around 80% of the code in the src folder.
The text was updated successfully, but these errors were encountered:
Hello, I am interested in this task but have some questions still not clear to me how to do it.
Is it possible to have a better idea about how many tests we are looking for? I was adviced to ask here on github since I might have a wrong idea about what's to be done. It would be good to know what type of testing we are doing, this is CLI commands testing, for example say we have a typical subcommand with 2 arguments and values for a subcommand "--address 'ADDRESS'
--key 'KEY' ", how many combinations and testing values are we doing, how "exhaustive" so to speak, depending on this the reward might be too low for the task.
I would appreciate if someone could offer support on this issue. Thank you.
The cli-rs do not count with unit testing, so it is required to write tests that can be run with the
cargo test
command and that test behaviors at the command line. These should be exhaustive, meaning they should test for all the commands and options combinations and provide an acceptable coverage level, i.e., around 80% of the code in thesrc
folder.The text was updated successfully, but these errors were encountered: