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

[Feature] Add flags to leo test #277

Closed
collinc97 opened this issue Aug 20, 2020 · 1 comment
Closed

[Feature] Add flags to leo test #277

collinc97 opened this issue Aug 20, 2020 · 1 comment
Assignees
Labels
feature A new feature.

Comments

@collinc97
Copy link
Collaborator

collinc97 commented Aug 20, 2020

🚀 Feature

Add file -f $FILE flag to run tests in specific file. Where $FILE is the name of the file.
Add input -i $INPUT flag to run tests with or without inputs. $INPUT is a boolean true or false.

Motivation

Currently the leo test command runs all tests in the main.leo file only.
Functionality should be added to run tests in a specific file and toggle tests with or without input.

Implementation

Add cli argument and file parsing logic to Leo CLI.

@collinc97 collinc97 added the feature A new feature. label Aug 20, 2020
@collinc97 collinc97 self-assigned this Aug 20, 2020
@damons damons assigned damirka and unassigned collinc97 Jan 22, 2021
damirka added a commit that referenced this issue Feb 8, 2021
Features:

- introduces new Command and Route traits for Leo commands and Aleo PM API
- most of the CLI code replace with higher-level abstraction - StructOpt
- anyhow used for error handling, no more custom error classes
- improves API - now every status code has its business logic
- adds global flags (e.g. --quiet to suppress output)
- error messages improved for convenience and better user experience

Closes:

- #604
- #599
- #584
- #277
- #376
@collinc97
Copy link
Collaborator Author

Closed by #632

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

Successfully merging a pull request may close this issue.

2 participants