-
Notifications
You must be signed in to change notification settings - Fork 53
Test Framework #80
Comments
Thinking out loud here, but I had good experience testing and contributing to a Jenkins API using a Travis-CI build file: https://github.com/bndr/gojenkins/blob/master/.travis.yml |
We are using drone for testing |
I think that's a great start, but I probably should have pointed to what I liked about the Travis setup:
The Jenkins instance is running, so the tests work against it with a known login, etc.. I don't see any of that in the drone config. Do the sections in the pipeline all run within the same context? Can a gitea server be run in the background so the other steps in the pipeline can run a test against a running instance? Also, does the Gitea SDK client need a token generated, or can it use a default user created with |
Spinning up |
I'm currently using gitea as a service (GaaS 😂 ) for testing the migration tool. I've created a seperate docker image containing a gitea instance which is already set up. gitea-service: https://git.jonasfranz.software/JonasFranzDEV/gitea-service PR with gitea-service tests: https://git.jonasfranz.software/JonasFranzDEV/gitea-github-migrator/pulls/5 |
How can someone set up a test environment for adding tests to this SDK? I'm at a loss as I don't quite understand how the main gitea project is doing tests. I'd think it's possible to do something with Docker, but I'm not terribly confident that you can spin up a gitea server and then run
go test
with it.Would it be possible to set up something equivalent to a golden file/db so you could use it as a baseline for tests?
The text was updated successfully, but these errors were encountered: