-
Notifications
You must be signed in to change notification settings - Fork 52
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
Support loading test cases from git repository #103
Comments
Read raw data from a git respository and unmarshall the raw content into Suits ? |
Yes, I'm thinking about making a git repository as the storage backend. So, we don't have a central storage. And users could choose a private git repository to store their test cases. For example, store them into a private Gitlab. |
Get it. Let me try to create a pr to handle it |
Sure. I'm looking forward it. |
I have a question: atest run -p https://github.com/LinuxSuRen/api-testing/tree/master/sample the |
In my view, some basic information of a git repo are necessary. Such as: repo URL, branch name, directory. For a private git repository, the auth is required as well. |
hi @cestlive , you can create a new extension with the git feature. See also the existing ones: https://github.com/LinuxSuRen/api-testing/tree/master/extensions |
go-git/go-git is a good candidate too. For the extension part, developers could get the connection information from the following code: api-testing/extensions/store-orm/main.go Line 85 in 1e45dd1
|
Another solution is that making git repository as a SQL server. Such as: dolthub/dolt. |
hi @cestlive , I'm going to take over this due to no active response in 3 month. Feel free to join me if you're still intested in it. |
Expected usage:
atest run -p https://github.com/LinuxSuRen/api-testing/tree/master/sample --auth personal-token
We need to consider the git branch and auth. Usually, the branch name could found from the URL. We could manipulate the git repository via jenkins-x/go-scm.
UI
In many cases, people will deploy a private Gitlab, and provide it to the team. Having an oauth integration might be a good idea for the users. They could login with their own account. So, we don't need to consider the user management.
See also the similar issue #94
The text was updated successfully, but these errors were encountered: