GithubHelp home page GithubHelp logo

Comments (3)

lattejed avatar lattejed commented on August 27, 2024 1
--match-path <PATH_PATTERN>
    only run test methods in source files at path matching regex. Requires absolute path

--no-match-path <PATH_PATTERN_INVERSE>
    only run test methods in source files at path not matching regex. Requires absolute path

They require an absolute path. Internally that pattern gets prefixed with a ^ and matched against the absolute paths of contract source files.

If the ergonomics of that are too awkward, feel free to file an issue. I can revisit that

from book.

rootulp avatar rootulp commented on August 27, 2024 1

Thanks! It works as expected now.

$ forge test --match-path '/Users/rootulp/git/hello_foundry/src/test/*'
compiling...
no files changed, compilation skipped.
Running 1 test for ContractA.json:ContractA
[PASS] testA() (gas: 120)

Running 1 test for ContractB.json:ContractB
[PASS] testB() (gas: 120)

Running 1 test for ContractC.json:ContractC
[PASS] testC() (gas: 142)

$ forge test --no-match-path '/Users/rootulp/git/hello_foundry/src/test/*'
compiling...
no files changed, compilation skipped.

from book.

rootulp avatar rootulp commented on August 27, 2024

I took a stab at documenting this but I'm observing unexpected behavior. I have a forge project that looks like

$ tree .
...
└── src
    ├── Contract.sol
    └── test
        ├── ContractA.t.sol
        ├── ContractB.t.sol
        └── ContractC.t.sol

I'm observing no tests run when I expect all three tests to run

$ forge test --match-path './src/test/*'
compiling...
no files changed, compilation skipped.

I'm observing no tests run when I expect testA to run

> forge test --match-path './src/test/ContractA.t.sol'
compiling...
no files changed, compilation skipped.

I'm observing all tests run when I expect no tests to run

$ forge test --no-match-path './src/test/*'
compiling...
no files changed, compilation skipped.
Running 1 test for ContractA.json:ContractA
[PASS] testA() (gas: 120)

Running 1 test for ContractB.json:ContractB
[PASS] testB() (gas: 120)

Running 1 test for ContractC.json:ContractC
[PASS] testC() (gas: 142)

@lattejed can you please help me understand if I'm using these flags incorrectly?

from book.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.