Integration tests for PR functionality when issues are disabled #1153

New Issue

GiteaMirror · 2025-11-02T03:50:19-06:00

GiteaMirror commented

2025-11-02 03:50:19 -06:00

Originally created by @lafriks on GitHub (Oct 16, 2017).

Need integration tests for #2710

Originally created by @lafriks on GitHub (Oct 16, 2017). Need integration tests for #2710

GiteaMirror added the type/testing issue/stale labels 2025-11-02 03:50:19 -06:00

GiteaMirror closed this issue

2025-11-02 03:50:19 -06:00

GiteaMirror commented

2025-11-02 03:50:20 -06:00

@jonasfranz commented on GitHub (Oct 17, 2017):

I've created some tests. But I'am not sure if they work properly and if they test everything needed.

My branch: https://github.com/go-gitea/gitea/compare/master...JonasFranzDEV:integration-test-pr?expand=1

Is there a good way to test integration tests locally? drone cli does not work for some reason.

@jonasfranz commented on GitHub (Oct 17, 2017): I've created some tests. But I'am not sure if they work properly and if they test everything needed. My branch: https://github.com/go-gitea/gitea/compare/master...JonasFranzDEV:integration-test-pr?expand=1 Is there a good way to test integration tests locally? drone cli does not work for some reason.

GiteaMirror commented

2025-11-02 03:50:20 -06:00

@Morlinest commented on GitHub (Oct 17, 2017):

@JonasFranzDEV You can run it same as make test but you need database up and running. I use 2 docker containers (gitea and db) on same custom network.

@Morlinest commented on GitHub (Oct 17, 2017): @JonasFranzDEV You can run it same as `make test` but you need database up and running. I use 2 docker containers (gitea and db) on same custom network.

GiteaMirror commented

2025-11-02 03:50:21 -06:00

@jonasfranz commented on GitHub (Oct 17, 2017):

@Morlinest could you send me your docker commands or docker-compose file?

@jonasfranz commented on GitHub (Oct 17, 2017): @Morlinest could you send me your docker commands or docker-compose file?

GiteaMirror commented

2025-11-02 03:50:21 -06:00

@Morlinest commented on GitHub (Oct 17, 2017):

@JonasFranzDEV I am using my own image (#2377), but you can try something like this (I can't test it because I can't mount local volumes now):

docker network create gitea-test
docker run -d --rm --net gitea-test -e POSTGRES_DB=test --name pgsql postgres:9.5
docker run -i --rm --net gitea-test -v <MY-PROJECT-PATH>:/srv/app/src/code.gitea.io/gitea -w /srv/app/src/code.gitea.io/gitea --net gitea -e TAGS="bindata" webh
ippie/golang:edge make clean generate build test-pgsql

Change <MY-PROJECT-PATH> for your path to project.

@Morlinest commented on GitHub (Oct 17, 2017): @JonasFranzDEV I am using my own image (#2377), but you can try something like this (I can't test it because I can't mount local volumes now): ``` docker network create gitea-test docker run -d --rm --net gitea-test -e POSTGRES_DB=test --name pgsql postgres:9.5 docker run -i --rm --net gitea-test -v <MY-PROJECT-PATH>:/srv/app/src/code.gitea.io/gitea -w /srv/app/src/code.gitea.io/gitea --net gitea -e TAGS="bindata" webh ippie/golang:edge make clean generate build test-pgsql ``` Change `<MY-PROJECT-PATH>` for your path to project.

GiteaMirror commented

2025-11-02 03:50:21 -06:00

@lafriks commented on GitHub (Oct 17, 2017):

This issue is about that that when issues in repository is disabled in PR it was not possible (tests must test that is possible) to:

Add/remove labels
Set/remove milestone
Set/remove assignee
Add/change/delete comment
Start/stop/add timetracking
Close PR
Multi-PR actions from PR list

@lafriks commented on GitHub (Oct 17, 2017): This issue is about that that when issues in repository is disabled in PR it was not possible (tests must test that is possible) to: * Add/remove labels * Set/remove milestone * Set/remove assignee * Add/change/delete comment * Start/stop/add timetracking * Close PR * Multi-PR actions from PR list

GiteaMirror commented

2025-11-02 03:50:21 -06:00

@stale[bot] commented on GitHub (Feb 11, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 11, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 03:50:22 -06:00

@stale[bot] commented on GitHub (Feb 26, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Feb 26, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror referenced this issue

2025-11-02 11:54:37 -06:00

[PR #1153] [MERGED] Fix double borders on edit page (#1152) #15789

Sign in to join this conversation.