Comments (1)
hey @drewgonzales360 - I've resisted going down this path for a few reasons:
Most importantly: it's important that the version of the ginkgo cli and the ginkgo library match exactly. The contract between the cli and the library is not subject to semver and can change at any time. today the recommendation is to go install
or, even better, go run github.com/onsi/ginkgo/v2/ginkgo ...
as that will pick up the same version of ginkgo as the library in go.mod
. Decoupling the two could be problematic and potentially confusing to users.
Secondarily: I've never thought this would be necessary. Ginkgo runs tests and so it either needs to compile the tests (in which case the go toolchain needs to be present on the machine anyway, so we can always go run
or go install
the ginkgo cli as mentioned above). Or Ginkgo needs to be pointed at a precompiled test binary. But if the user can compile a test binary with the correct GOARCH
and GOOS
then they can correctly compile the ginkgo cli of the correct and ship it to their target platform.
So I suppose I'd love to learn more about your usecase, given that second point. What are the reasons you can't compile ginkgo on demand or at the same time that you precompile your test binary?
from ginkgo.
Related Issues (20)
- Is there a way to have a single suite that will run tests in sub packages? HOT 2
- Getwd() breaks test caching on build runners like Buildkite HOT 1
- Get coverage from ginkgo
- DeferCleanup() blocks are run after all AfterEach() blocks, regardless of nesting HOT 2
- Is there a way to populate dynamic data in the Tree Construction Phase? HOT 2
- Detail Skipped reason when spec is skipped by cli arguments HOT 6
- Support customizing the SpecContext HOT 4
- ginkgo v2 leaks goroutine HOT 3
- Proposal: RunSpecsWithContext? HOT 14
- Add option to StandardReporter to display things better on github actions HOT 2
- Call dynamic variables through 2 test files. HOT 1
- Skip each test function logs and print in summary HOT 1
- Run a single suite with N instances in parallel with different `BeforeSuite` Setup. HOT 3
- Feeding report back for focusing on failed test-cases HOT 1
- Junit report should have system-out HOT 1
- could not log in Eventually with fmt.Fprintf(GinkgoWriter) HOT 3
- Question: One Suite to rule them all HOT 2
- when using concurrency, a test case failure in a background go routine does not show which test case failed HOT 3
- Add cli flag to fail when no tests were run HOT 1
- `ginko -p 2` does not complain about having an extra argument
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ginkgo.