Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
1c2b7374
Commit
1c2b7374
authored
Feb 18, 2016
by
Jacob Vosmaer
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add test guidelines
parent
8a339b46
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
9 additions
and
30 deletions
+9
-30
README.md
README.md
+9
-30
No files found.
README.md
View file @
1c2b7374
...
@@ -70,42 +70,21 @@ make install PREFIX=/foo
...
@@ -70,42 +70,21 @@ make install PREFIX=/foo
## Tests
## Tests
```
Run the tests with:
make clean test
```
## Try it out
You can try out the Git server without authentication as follows:
```
```
# Start a fake auth backend that allows everything/everybody
make clean test
make test/data/test.git
go run support/fake-auth-backend.go ~+/test/data/test.git &
# Start gitlab-workhorse
make
./gitlab-workhorse
```
```
Now you can try things like:
### Coverage / what to test
```
Each feature in gitlab-workhorse should have an integration test that
git clone http://localhost:8181/test.git
verifies that the feature 'kicks in' on the right requests and leaves
curl -JO http://localhost:8181/test/repository/archive.zip
other requests unaffected. It is better to also have package-level tests
```
for specific behavior but the high-level integration tests should have
the first priority during development.
## Example request flow
It is OK if a feature is only covered by integration tests.
-
start POST repo.git/git-receive-pack to NGINX
-
..start POST repo.git/git-receive-pack to gitlab-workhorse
-
....start POST repo.git/git-receive-pack to Unicorn for auth
-
....end POST to Unicorn for auth
-
....start git-receive-pack process from gitlab-workhorse
-
......start POST /api/v3/internal/allowed to Unicorn from Git hook (check protected branches)
-
......end POST to Unicorn from Git hook
-
....end git-receive-pack process
-
..end POST to gitlab-workhorse
-
end POST to NGINX
## License
## License
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment