-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Git Operations Test Server #335
Labels
area/git
Git and SSH related issues and pull requests
Comments
The Git Test Server should also ignore the value of |
Now are are in course to be mono git implementation, a lot of this could actually be implemented and upstreamed. The E2E use cases would be enough to detect changes problems. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The test coverage around git operations heavily relies on gitkit for self-contained tests. For E2E tests we also rely on directly accessing SaaS providers (e.g. GitHub) to ensure that our git implementation is consistently working across all out supported platforms.
Unfortunately, different SaaS providers support a different range of crypto algorithms, Git protocol versions, etc. Our upstream dependencies may introduce changes that may break specific features with said SaaS providers.
Instead of creating E2E tests for every single major SaaS provider, we could instead create or improving the existing git server to enable us to test features we want to support, and therefore quickly understand regression before releasing changes.
Below is a brain dump of specific features that are based on different issues that users have reported, and ideally a git test server would support:
These items should enable the test coverage to extend to support each one of the points above.
The text was updated successfully, but these errors were encountered: