[Bug] "No such file or directory (os error 2)" when running leo test on a fresh --lib project

[aphelionz]

🐛 Bug Report

I'm getting a "No such file or directory (os error 2)" after running leo new lib --testing and then running leo test.

Steps to Reproduce

AleoHQ/  $ leo new --lib testing
Initializing Successfully initialized package "testing"


 AleoHQ/  $ cd testing/

 testing/  $ leo test
      Test reading: No such file or directory (os error 2)

Error: InputsDirectoryError(Reading(Os { code: 2, kind: NotFound, message: "No such file or directory" }))

Expected Behavior

I would expect to see the default output:

      Test Running 0 tests
      Done Tests passed in 3 milliseconds. 0 passed; 0 failed;

Your Environment

• 1.0.3
• 1.46.0 stable
• Ubuntu 20.04

[damirka]

Starting a conversation on this one. Are we keeping --lib option in a CLI and how do we deal with tests with inputs?

My proposed solution is:

1. Make inputs optional in testing libraries (i.e. projects that do not contain main.leo file). In the end circuits can be unit-tested and it is okay (?) to not provide inputs for libraries. Adding a warning message of kind No inputs found may also be helpful in this scenario.

2. I would also improve @collinc97 proposal in [Feature] Add flags to leo test #277 and allow people write tests in any file. So leo test could be called for specific file(s) or even all files in the project (if there're tests of course): leo test --all and leo test -f lib.leo -f tests.leo. Inputs for these tests are still optionally provided.

@collinc97 @damons @howardwu what do you think? Maybe there's something I don't know yet?

[collinc97]

Closed by #632