Document that `test/commands` and `run_test.{sh,bat}` cannot coexist
See original GitHub issueAs title. If meta.yaml
has the test/commands
session
test:
commands:
- ...
but run_test.{sh,bat}
is also provided, the commands in test/commands
will not be run. Workarounds include
- Move all commands to
run_test.{sh,bat}
(or vice versa) - Rename
run_test.{sh,bat}
to something else and run it explicitly
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
dotnet test command - .NET CLI | Microsoft Learn
The dotnet test command is used to execute unit tests in a given project.
Read more >How to run test cases in a specified file? - Stack Overflow
There are two ways. The easy one is to use the -run flag and provide a pattern matching names of the tests you...
Read more >Test from the command line | Android Developers
This document describes how to run tests directly from the command line. This document assumes that you already know how to create an ......
Read more >Add a test - The Go Programming Language
The go test command executes test functions (whose names begin with Test ) in test files (whose names end with _test.go). You can...
Read more >ng test - Angular
Option Description Value Type Defau...
‑‑browsers Override which browsers tests are run against. string
‑‑code‑coverage Output a code coverage report. boolean false
‑‑code‑coverage‑exclude Globs to exclude...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah have a few reproducers now. Tried submitting a fix upstream. Could use a review if you have time to look 🙂
Sorry I don’t remember in which feedstock I hit the issue, but I seem to remember confirming it’s a known issue with either @jaimergp or @beckermr on the Gitter channel back then before filing an issue.