Test Framework #80

New Issue

lunny · 2017-11-25T15:42:20Z

lunny commented

2017-11-25 15:42:20 +00:00

Author: @klauern

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?

Author: @klauern  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](https://medium.com/@povilasve/go-advanced-tips-tricks-a872503ac859) so you could use it as a baseline for tests?

lunny commented

2017-11-25 15:59:49 +00:00

Author: @klauern

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

Author: @klauern 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

lunny commented

2017-11-25 23:24:14 +00:00

Author: @lafriks

We are using drone for testing

Author: @lafriks We are using drone for testing

lunny commented

2017-11-25 23:25:01 +00:00

Author: @lafriks

https://github.com/go-gitea/go-sdk/blob/master/.drone.yml

Author: @lafriks https://github.com/go-gitea/go-sdk/blob/master/.drone.yml

lunny commented

2017-11-26 00:04:48 +00:00

Author: @klauern

I think that's a great start, but I probably should have pointed to what I liked about the Travis setup:

  - docker run -d --name=jenkins -p 8080:8080 --env JAVA_OPTS=-Djenkins.install.runSetupWizard=false gojenkins

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 gitea admin create-user? What's the hands-free way to do that?

Author: @klauern I think that's a great start, but I probably should have pointed to what I liked about the Travis setup: ``` - docker run -d --name=jenkins -p 8080:8080 --env JAVA_OPTS=-Djenkins.install.runSetupWizard=false gojenkins ``` 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 `gitea admin create-user`? What's the hands-free way to do that?

lunny commented

2017-12-03 20:11:22 +00:00

Author: @bkcsoft

Spinning up gitea/gitea:master as a service for running tests in easy enough. Someone just have to make tests ;)

Author: @bkcsoft Spinning up `gitea/gitea:master` as a service for running tests in easy enough. Someone just have to make tests ;)

lunny commented

2018-06-15 12:17:19 +00:00

Author: @jonasfranz

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

Author: @jonasfranz I'm currently using gitea as a service (GaaS :joy: ) 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

lunny added the

kind/testing

label 2019-11-05 13:21:43 +00:00

lunny referenced this issue

2019-11-06 13:04:59 +00:00

Add test framework #194

techknowlogick referenced a pull request that will close this issue

2020-01-10 21:44:51 +00:00

Add test framework #227

6543 added this to the v0.11.0 milestone 2020-01-12 13:09:37 +00:00

techknowlogick closed this issue

2020-01-13 17:17:57 +00:00