E2E testing on Windows
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 461
- Forks
- 277
- Avg merge
- 16h 48m
- Merged PRs (30d)
- 95
Description
Version and Operating System
Both release and HEAD versions, running on Windows.
Expected Behavior
tkn, and its chocolatey package, are able to be tested when a PR is created or a release is cut.
Actual Behavior
At the moment we don't have windows machines to call out to for running tests. Near-term we could use another CI service like Circle or Travis. Longer term it would be great to get a Tekton task running the tests on Windows or calling out to an external service to run tests.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the current release and pull-request testing setup, then compare available CI services with the proposed Tekton task or external Windows service. Done means Windows end-to-end tests run for pull requests and releases, including the Chocolatey package.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, cli, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100