Make integration tests more user-friendly

[ethantkoenig]

Check that ./gitea binary exists, and don't print buffer.String() in assert message, since the buffer may contain an entire HTML page.

[lafriks]

LGTM

[codecov-io]

Codecov Report

❗ No coverage uploaded for pull request base (master@b0f7457). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #2536   +/-   ##
=========================================
  Coverage          ?   26.96%           
=========================================
  Files             ?       84           
  Lines             ?    16906           
  Branches          ?        0           
=========================================
  Hits              ?     4559           
  Misses            ?    11672           
  Partials          ?      675

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b0f7457...a303b89. Read the comment docs.

[lunny]

I think we should find a method to only run one integration test function.

[sapk]

@lunny It is possible manually like any go test (with little sugar ^^) : go test -c code.gitea.io/gitea/integrations -o integrations.sqlite.test -tags 'sqlite' && GITEA_ROOT="$GOPATH/src/code.gitea.io/gitea" GITEA_CONF=integrations/sqlite.ini ./integrations.sqlite.test -test.v -test.run GPG

[sapk]

LGTM

[lunny]

@sapk I know that, I mean a friendly method.

[sapk]

@lunny Maybe by adding local arg for test TEST_MASK ?